Skip to main content

05 / Service


Sharing knowledge and insights exponentially increases progress on any project. But we get it - writing it all down is tedious, and no one really did it in your company. That’s why we take it upon ourselves to structure and write product documentation and keep your whole company updated about the why, how and what we are doing.

Benefits of documentation

The ultimate benefit of documentation is that you can build digital products faster and with less error. And here are a few more:

  • Alignment & transparency between teams
    All teams are aligned on decisions and responsibilities.
  • Spend less time in meetings
    Save time from catch-up meetings by reading and collaborating asynchronously.
  • Avoid having the same discussions
    Insights, discussions and decisions are accessible and easily searchable by everyone.
  • Faster onboarding of newcomers
    All historical context is readily available for anyone to get up to speed.

Oh yes, we create documentation in the tool you’re using. Whether that’s Notion, Gitbook, Confluence, or Word… (but please don’t let it be Word).

We document all that matters

  • 01 / Documentation service

    Product strategy

    Based on your product vision, we clearly document the strategy on why your product is built, who you've built it for, and what it can do along with visualisations of how your product could look in the future.

  • 02 / Documentation service

    Feature passports

    We document all feature specifications in one place so everyone involved can easily get up to speed on why the feature is needed, what defines the success of the feature, and how we can measure it.

  • 03 / Documentation service

    Research insights

    We extract insights from quantitive or qualitative research and document all findings in one place, along with the answers to all your big questions we've defined together in the beginning of the research.

How we structure our documentations

  • 01 / Section

    Define business rationale

    To start, we provide a clear understanding of what problems (opportunities) we are solving (pursuing), whom we are doing it for, and what values we deliver to them. This information is usually gained through research.

  • 02 / Section

    Use cases, requirements, current scope and long-term vision

    We list out all the use cases, jobs to be done, and what was in and out of the current scope. This way all teams know what is expected from them at any point. And we also include future iterations and where we aim to go with the feature.

  • 03 / Section

    Designs and user flows

    We share all links to our designs and include other necessary visuals, such as user journeys. It should be easily understandable by anyone, regardless of their prior knowledge of the product.

  • 04 / Section

    What does success look like and how to measure them

    We define the success criteria of every feature / design / idea and ways to measure them so everyone knows where the goal post is.

  • 05 / Section

    Research and user testing learnings

    We document all insights gained, user behaviour patterns learnt, and feedback gathered, together with the objectives defined at the beginning of the research project.

  • 06 / Section

    Open questions and known issues

    At every step of the process, we list the open questions and issues with the answers we collect along the way. This way, we ensure no one has to answer the same question twice.


Let’s hop on a call

I'm Hannes, by the way.

Getting to know each other is a good way to start. During our call,
we will discuss your goals, how we can help and when we’ll open the