Skip to content

Website and service development

We develop journeys, features, editorial tools and the technical foundation of existing websites and services. We study what already works and choose useful improvements with your team.

An operating product already has experience

We begin by studying the existing product and the experience of people who use and work with it. We learn why earlier decisions were made and what has changed since then.

With your team, we choose an improvement that can simplify an important journey, make publishing easier, open a useful capability or remove a technical constraint.

Understand causes before changing the form

A design that looks inconvenient at first may support an important part of the process. A feature may go unused because maintaining it demands too much staff effort.

We examine the causes so we can preserve what works and choose an improvement that solves the actual problem.

A change gets a testable purpose

Before release, we agree on what should improve and how we will tell. We record the baseline, implement the chosen change and compare the result under comparable conditions.

Based on the findings, we decide whether to continue in the same direction, adjust the solution or finish the work. We also consider other events during the period that may have affected the measures.

From observation to the next evidence-based decision

  1. State the expectation

    Task, baseline and comparison method

  2. Make the change

    Release the chosen solution

  3. Study the result

    Continue, adjust or stop

Choose the scale of transition with evidence

There is no need to preserve the old foundation at any cost. If it limits development, we compare a local change, replacement of one part and migration. We account for transition cost, ongoing expenses, team work and external dependencies.

We prepare tests and a rollback procedure for the release. During a migration, we separately verify data, relationships and addresses. We compare options by product capability, cost and the work ahead for the team.

Findings carry into the next task

We record what we wanted to improve, why we chose this approach and what we learned after release. With the people who will continue development, we discuss which findings apply and which assumptions need another test.

Alongside product and code changes, we hand over test results, a comparison of measures and documentation. The team can use this accumulated understanding in its next task.

Our involvement can have a clear boundary

We define a finished result for the work together: a chosen direction, a released improvement or a method the team has learned to use.

After handover, you have an updated product and an understanding of what has already been tested and which questions to examine in the next change.

What the work may include

  • Easier ordering

    Fix the steps where customers drop out.

  • Faster website

    Optimise page loads and heavy media.

  • Independent editing

    Tools for updates by your own team.

  • Migration and renewal

    Move data and features to a suitable foundation.

How the work is organised

Study the current product

We examine the relevant part of the product with your team. We study code, usage data and costs, and learn why earlier decisions were made.

From you
Source code, usage data, costs and team participation
Stage outcome
Description of the current state and problems found

Choose an improvement

We compare ways to solve the problem. We agree on the result, scope, cost and method of verification.

From you
Product owner’s priorities and participation of employees whose work will change
Stage outcome
Improvement plan, cost estimate and acceptance criteria

Release the change

We implement the improvement and test it alongside existing features. We prepare a way to return to the previous version if something goes wrong.

From you
Access, materials and an agreed release window
Stage outcome
Released improvement, test results and rollback instructions

Assess the result

We compare measures before and after release. We discuss the findings with the team and decide what to do next.

From you
Postrelease data and participation of the product owner
Stage outcome
Results comparison, record of decisions and next tasks

What we check

  • Release

    We agree on launch, tests and a rollback procedure.

  • Data and connections

    We check data integrity, integrations and addresses.

  • Effect

    We compare speed, cost and user actions.

What we hand over

  • Source files and project repository
  • Access credentials and a list of external integrations
  • Update and recovery instructions
  • Documents covering rights and licences used
  • Change report, baseline measures and a development plan.

What would you like to improve in the product?

Show us your existing website or service and tell us what you want to change. We will define the area, available data and your team’s role to choose the first complete step.

hello@tok.moscow@TokMoscowBot
Discuss a project

After agreeing the work

  • Task list and examples of problems
  • Documentation and current infrastructure diagram
  • Responsible person and agreed access to code and environments

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.