PROTANO00 · TANGLEGet in touchContact

Making
complex
feel simple.

Stakeholders, a legacy system, regulations and a deadline. I untangle it into one clear route — then design and build the product that runs on it.

6 THREADS · NO DIRECTION
StakeholdersLegacy systemUsersRegulationDataDeadlineUnderstandStructureDesignPrototypeBuildImprove010203040506StakeholdersLegacy systemUsersRegulationDataDeadline
Scroll to untangle ↓
PHASE 01 / 06

Understand

Understand first. Then make something.

Every project starts with the question behind the question. I talk to stakeholders and users, read the data and walk through the existing service myself. Assumptions go next to facts.

IN THIS PHASE
  • Product strategy
  • Discovery
  • UX research
  • Service design
  • Stakeholder sessions
  1. Who uses this, and when?
  2. Where do people drop off today?
  3. What should be different a year from now?
  4. Which systems and rules are already in place?
  5. What is the smallest version that delivers value?
OUTCOME

One sharp problem, a measurable goal and the risks on the table.

PHASE 02 / 06

Structure

No loose screens. Route first.

Before anything is visually designed, I map out the steps, choices and exceptions. That shows where things get stuck today — and how it can be simpler.

IN THIS PHASE
  • Customer journeys
  • Information architecture
  • User flows
  • Wireframes
  • Content structure
USER FLOW · APPLICATIONMain routeException
Incomplete → back, with guidanceUnclear → manual review
STEP 02DetailsON THIS SCREENName, email and one open question. Errors right at the field.DESIGN RULEOnly ask what this step truly needs.
PHASE 03 / 06

Design

An interface that shows just enough.

Only when the route is right do I design the interface: hierarchy, interaction, copy and accessibility at once. Every component gets all of its states, so nothing is left to guess during the build.

IN THIS PHASE
  • UX/UI design
  • Interaction design
  • Responsive design
  • UX writing
  • Motion
  • Accessibility
COMPONENT · SIGN-UP FIELD1 component · 7 states
STATE · DEFAULT
Email address
name@company.com
Send
one field · one primary action

Calm and clear: one field, one primary action.

PHASE 04 / 06

Prototype

Test before it costs money.

A clickable prototype feels like the real product. I test it with real users and watch where they hesitate or drop off. Decisions are based on behaviour, not preference.

IN THIS PHASE
  • Clickable prototypes
  • Usability testing
  • Iteration
  • Stakeholder validation
PROTOTYPE · ANNOTATED WIREFRAMEA question in clickable form
WHAT THIS TEST ANSWERS
  1. 1ProgressDo three named steps feel short enough to start?
  2. 2Label above the fieldDo people fill it in without hesitating?
  3. 3Inline errorDo people fix it on their own?
  4. 4One primary actionIs it found on the first try?
  5. 5HotspotDashed = clickable. Every misclick tells us something.
PHASE 05 / 06

Build

I build what I design.

No handover to a team that never saw the design. I turn it into a design system and write the front-end myself — semantic, accessible and fast. Or I plug straight into your developers.

IN THIS PHASE
  • Design systems
  • Component libraries
  • Design tokens
  • Front-end
  • CMS
  • Websites, portals, webapps
TokensComponentsPatternsPages

Every component has the same name in design as in code. The sign-up field from phase 03 is exactly the field you fill in at the bottom of this page.

PHASE 06 / 06

Improve

Launch is the start, not the finish.

After launch I measure what happens, compare design with what was built and improve in short cycles. A product is never finished — but it keeps getting better.

IN THIS PHASE
  • Design QA
  • Measure
  • Optimisation
  • Conversion
  • Continuous development
  1. 01Measure. Where do people drop off, what do they ignore?
  2. 02Learn. Design QA and data side by side: what’s off?
  3. 03Adjust. Small, focused releases. Then measure again.
WHO’S DRIVING

One person. The whole line.

Protano is not an agency with account managers and handovers. You work directly with the person who researches, designs and builds. That means nothing lost in translation, fewer meetings and no surprises.

Product designer
Decides what the product should do, and why.
UX specialist
Makes sure people understand it and finish it.
Design engineer
Builds it: accessible, fast and maintainable.
HOW IT STARTS
  1. 01Intro callHalf an hour about your knot. No obligation, no pitch.
  2. 02Route proposalWhich phases, in what order, with what timeline and cost.
  3. 03DepartureWe board at the phase your product is in right now.
FINAL STOP

Protano.
Designed to work.

Tell me what you’re working on and where you need help. That way the first conversation is about your product, not about me.

USEFUL TO MENTION
  1. 01What you’re working onA website, portal, web app or a service that spans all of them.
  2. 02Where it gets stuckThe step where users drop off, or where the team can’t agree.
  3. 03Who’s involvedStakeholders, existing systems, your own developers.
  4. 04When it needs to workA deadline, a launch or simply: as soon as possible.
OR EMAIL DIRECTLYhello@protano.com