Skip to content

Research and product design

We research and design digital products before development or ahead of a major change. We help choose a suitable solution and prepare materials your team can use to continue the work.

The question matters more than the volume of research

An idea or prototype can develop into several appealing products. We identify which distinction affects your choice and what must be learned about the first release, user work or costs.

We agree on the depth of testing needed to answer that question. Sometimes a short review is enough; in other cases we need to work with several groups of participants.

Test what changes the decision

We study enquiries, observations, statistics and process descriptions the team already has. We separate facts from assumptions and choose what needs clarification.

Questions about people’s behaviour are tested on a prototype with participants. For a technical task, we examine data, integrations and constraints. The results help confirm a direction, narrow it or reconsider the idea.

The consequences make the choice visible

We compare options by the problem they solve, what is needed to launch them and who will keep them running. We consider initial implementation, team effort and regular costs.

This defines the first release and the order of later steps. We record what has already been tested, which assumptions still support the decision and what could change the priorities. The prototype shows the agreed user journey through the product screens.

What accompanies a recommendation

MaterialHow it helps the team
Observation and sourceUnderstand what supports the finding and how broadly it applies
Comparison of optionsReconstruct the reasons for the choice and its limitations
Prototype and criteriaDiscuss implementation and check the agreed result
Open questionKnow what has not yet been proven and could change the decision

Explain the reasons behind decisions

We review the materials with the people who will continue the work. We explain why the scenario was chosen, which alternatives were considered and which requirements must be retained during implementation.

We hand over the prototype, requirements, test results and open questions within the agreed scope. We formulate acceptance criteria for discussing development. The outcome is a well-founded plan to build or change the product.

Continue with the team you choose

Research helps make a decision and explain it to others. Your team keeps editable materials and an understanding of where the requirements came from.

If circumstances change, you can revisit the rationale and revise the relevant part. The outcome may be to start development, run another test or postpone building the product.

What the work may include

  • New product

    Testing the main scenario before development.

  • Complex work process

    Map of actions, participants and exceptions.

  • Interface problem

    Finding why a task is not completed.

  • Preparing for development

    A shared set of requirements for the team and contractors.

How the work is organised

Examine the task

We establish which decision needs to be made and what prevents it now. We collect known facts and the questions that must be tested.

From you
Task description, available materials and constraints
Stage outcome
Research plan and list of questions

Test the assumptions

We choose a method that fits the task. This may involve studying a work process, testing a prototype with users or examining technical constraints.

From you
Data and participation from the people whose work the product will affect
Stage outcome
Observations and findings on the questions tested

Compare solutions

We assess options by their benefits and the cost of launch and ongoing work. We describe the chosen solution in enough detail for development.

From you
Participation from the product owner and company specialists
Stage outcome
Prototype, requirements, priorities and acceptance criteria

Hand over for development

We review the materials with the team that will build the product. We explain the reasons for the choice and note questions still to be resolved.

From you
Development team or person responsible for handing over the materials
Stage outcome
Editable materials and explanations of decisions

What we check

  • Users

    We test key scenarios with a prototype.

  • Requirements

    We document roles, data, accessibility and integrations.

  • Economics of the solution

    We compare launch scope and regular expenses.

What we hand over

  • Editable prototype and source materials within the agreed scope
  • Test results, observations and limitations of the findings
  • Requirements and acceptance criteria for the chosen scenario
  • Priorities, decision rationale and open questions
  • Implementation plan and review of materials with the chosen team

What decision do you need to make now?

Show us an idea, prototype or disputed part of a product. We will define the question, study the materials available and agree on the scope of testing.

hello@tok.moscow@TokMoscowBot
Discuss a project

After agreeing the work

  • Materials about the product and current process
  • Contact for the person responsible for the decision
  • Agreement that we can speak with participants

How would you like to get in touch?

Send an emailTell us about your project and attach any materials.hello@tok.moscowLeave a request in TelegramThe bot will ask a few questions and share your answers with the team.