01
Full project
Within an agreed scope, from product definition and design through to a working result and hand-over. Websites, mini-programs and interactive experiences all fit here.
For: commissions that want one thing built from start to finish.
Process
From brief to hand-over
From a clear goal to a finished hand-over, every step has a defined output and a confirmation. Scope is agreed before anything is built; if you need it live, that is done once the scope includes it.
Ways to work together
02
Design collaboration
Design files, flows and interaction notes, implemented by your team. Where useful, a clickable prototype or a working demo explains the key interactions; the demo validates the experience, and production scope is agreed separately.
For: teams with developers in place that need the product and experience worked out.
The five stages
01
Brief and scope
- What I do
- Work through the goal, the users and the material you already have.
- What you receive
- A scope note: what is included, what is not, how the work is staged and what each stage delivers.
- What you confirm
- Scope and stages.
02
Direction
- What I do
- Structure and visual direction, a few comparable options.
- What you receive
- Information architecture sketches and direction drafts.
- What you confirm
- One direction.
03
Product and experience
- What I do
- Key paths, states and edge cases, interface framework.
- What you receive
- Flow diagrams and key screens.
- What you confirm
- The flows and the interface framework.
04
Design and build
- What I do
- Final visual design; for full projects, implementation section by section.
- What you receive
- Final Figma files, preview links per section, or a working demo.
- What you confirm
- Feedback per section before the next one starts.
05
Review and hand-over
- What I do
- Organise source files and the delivery list; if the scope includes going live, help with that.
- What you receive
- Design source files, code and documentation.
- What you confirm
- Sign-off.
An example of trimming the stages
A camera interaction for an exhibition stand: direction and product stages usually merge into one "rules plus feedback" prototype, checked for feel on a real device, before final design and on-site adaptation. Stages can merge or split per project; the confirmation points stay.
Questions
- How is pricing set?
- We talk through the goal, scope and deliverables first. I reply with a scope note, and the plan, timeline and price come with it. There is no public price list.
- How are timeline and revisions set?
- The scope note states the timeline per stage and the confirmation point for each. Revisions happen before each stage is confirmed; requests outside the scope are assessed separately.
- What about source files and usage?
- Deliverables, source files and the scope of use are written into the agreement before work starts and followed once both sides confirm.
- Can you work with our developers?
- Yes. Design collaboration exists for that: I provide design files and interaction notes, a demo where needed, and answer questions during implementation.
Tell me about your project
The goal, the expected deliverable and references are enough to start.
Go to contact