Frame
A few conversations where we answer the basics together: which problem, for whom, how it is solved today, what is out of the first version. Result: a one-page brief and a hypothesis list.
HomeMethod
Method
Every step ends with a decision point. You control the pace, the scope and the moment to stop.

A few conversations where we answer the basics together: which problem, for whom, how it is solved today, what is out of the first version. Result: a one-page brief and a hypothesis list.
We describe user paths: first open, key action, return. A screen map grows from them. Real scope and unnecessary features become visible here.
A clickable prototype without colour or decoration — to test logic with a few people from the target audience. Then a visual system and final layouts.
Development in short stages with a demo after each. You receive test builds and can hand them to first users.
Publishing preparation, replying to review feedback, then support under an agreed plan.
What is done, what is next, which questions are open. In writing, so you can return to it.
A working result shown.
Kyiv time.
itgroup@averiksit.win
New instead of old, not on top.
Layouts, code, access and documentation are handed over when work is complete.
If something threatens time or scope — you hear about it straight away.
The priority board in the lab is a simplified version of what we do at the scenario stage.
To the priority board