palmscout: work begins before the contract is signed.
A workshop note on the product vision. palmscout connects recruiting, HR and staffing, with decisions tested against practical handovers between people rather than feature lists.
Read the German original
A product in development, deliberately visible
palmscout is a product developed independently by neurofunken. Its vision connects recruiting, personnel administration, staffing, job search and collaboration with employers. This note describes the direction of development. It announces neither available features nor a release date. We want to discuss the questions early, before selling promises.
The central product question is how people with different responsibilities can work together reliably on employment matters. A shared context should provide orientation. Each role needs an appropriate view of the information and next steps, suited to its particular work.
Take different perspectives seriously
People looking for work may need to understand a role and the status of an application. Employers need to clarify requirements and responsibilities. Staffing teams and HR support transitions, ask questions and coordinate agreements. These example needs are the starting point for product design, ahead of an abstract idea of an HR suite.
palmscout aims to bring these perspectives together while giving each role an appropriate interface and amount of information. Which details are needed for each task, and who may see them, are central design questions. The relationships between roles matter as much as the individual views.
Handovers are at the heart of the product
Imagine an interview after which feedback from the employer is still missing. The applicant wants to know whether they need to do anything. The staffing team needs to know who should follow up. The employer needs to see which decision remains open. The same case raises a different question for each participant. This is where software proves whether it helps people or merely records events.
We want situations like these to guide product decisions. A status is useful when people understand its meaning and can work out the next step. The number of records being managed says little about whether collaboration has become easier.
Design access for different people
Someone sending their first application has different experience from someone who has worked with personnel processes for years. Age alone does not explain those differences. Language, eyesight, technical experience and the device being used also affect how people can use an application.
The W3C Web Accessibility Initiative recommends considering accessibility, usability and inclusion together. For the palmscout vision, this means understandable terms, clearly recognisable actions and interaction paths that can be tested. These goals need technical checks and feedback from different people. Design intent alone does not demonstrate accessibility.
Test the idea through concrete tasks
Specific questions therefore guide further development: can people find the information they need? Do they recognise when details are missing? Can a handover be followed? A design should be assessed against tasks like these. Any SI assistance must also demonstrate its purpose. An early concept view can help uncover misunderstandings. Feedback should first be treated as material to learn from, then used to make justified changes.
We want to explain the direction of palmscout early and discuss actual development steps once they can be substantiated. Scope, access and availability will be described separately when established. Until then, this workshop note offers an insight into the questions that should guide the product.
What does this look like in your work?
We can turn the idea into a sensible next step with you.
Meet palmscout