Product Creation

We bring together the relevant stakeholders to clarify the initial idea, business context, known requirements and open questions. The workshop helps create a shared understanding of what the product is intended to achieve and which assumptions need to be investigated.

We speak with people who understand the organization, service or operational context from different perspectives. This helps uncover requirements, constraints, internal knowledge and conflicting expectations that may not be visible in the initial brief.

We review relevant products, services and established patterns to understand how similar problems are currently solved. The goal is not to copy competitors, but to identify expectations, gaps and opportunities for a more useful approach.

Where an existing product, prototype or comparable service is available, we assess it against recognized usability principles. This can reveal structural issues, unclear interactions and recurring friction before more extensive research or redesign begins.

We use interviews, observation, surveys, contextual inquiry or other suitable methods to understand the people the product is intended to support. Research explores their goals, behaviors, frustrations, language, mental models and current ways of solving the problem.

Existing analytics, usage data, surveys or other quantitative sources can help show how often particular behaviors occur and where larger patterns emerge. These findings complement qualitative research and help avoid relying on isolated observations.

We organise observations and evidence into themes, patterns and areas of opportunity. Methods such as affinity mapping help turn individual findings into a shared understanding that can guide the product direction.

Where useful, we translate the research into practical frameworks that describe relevant user groups, situations, motivations and desired outcomes. These become working tools for product decisions rather than demographic profiles for their own sake.

We define the core problem the product should address, including who experiences it, in which context and why current alternatives are insufficient. A clear problem definition helps prevent the product from becoming a collection of loosely connected features.

We establish a small set of principles that guide what the product should prioritize and how it should behave. These principles provide a consistent basis for evaluating ideas and making trade-offs throughout design and development.

We structure the product’s content, functions and navigation so that the system reflects how people understand and use it. This creates the foundation for clear flows and a coherent interface.

We map the steps people need to take to complete important tasks. The flows help clarify decisions, dependencies, system responses and potential points of friction before detailed interface design begins.

We explore the structure of screens and interactions without committing too early to visual detail. Wireframes make it possible to compare approaches, discuss functionality and refine the product logic efficiently.

We turn key flows into a realistic prototype that can be experienced and tested before development. This helps stakeholders understand the proposed product and allows interaction decisions to be evaluated in context.

We test the concept or prototype with representative users to see where it is clear, where it creates confusion and whether it supports the intended tasks. The findings are used to refine the product before implementation.

We translate the product direction into a focused first release. Features are prioritized according to user value, organisational goals, technical dependencies and what needs to be learned first.

Where required, the program can extend into detailed interface design with defined layouts, component states and interaction behavior. The result can be prepared for direct handover to an internal or external development team.

We distinguish between the first valuable release and possible later development. This creates a practical roadmap without pretending that every future feature can or should be decided at the beginning.