Skip to content
Illustrated portrait of Berker

Berker Agun

Product Design Lead · Stockholm

My portfolio is password protected, because it shows work from regulated products. 🔒

✉️ Ask me for the password
Berker Agun

How I work

The product design team runs on a written-down process. Every project moves through the same eight steps, so stakeholders always know where it stands and what happens next.

Start from a problem space
A brief states the business objective, the audience and the constraints, not a list of screens to draw.
Leave every meeting with owners
Workshops end with who does what, and by when. Vague next steps don’t count as an outcome.
Research outlives the project
Findings are tagged in a shared research base, so the next team starts ahead instead of from zero.

  1. Project brief

    The requester opens a brief in Jira with the business objective, target audience and primary constraints. The template also asks for goals and non-goals, what success looks like, edge cases and how results will be measured.

    Tools: Jira

  2. Kickoff workshop

    A time-boxed session with stakeholders in several countries validates the goals, non-goals and requirements. Pip Decks tactics such as the hypothesis statement turn assumptions into things we can test.

    Tools: Miro, Pip Decks

    • Checkpoint meeting

      Who / What / When

      Every commitment gets an owner, a task and a deadline before the workshop closes.

  3. Gather user data

    With the BI analyst we pull quantitative behaviour, then add qualitative insight from the research repository to see the friction from both sides.

    Tools: Looker, Sentry, GA4, Maze, Airtable

  4. Synthesis and opportunity mapping

    Research is grouped into cluster findings, turned into key recommendations, and tied to opportunities with a direct business effect. The Jira brief is updated with what we learned.

    Tools: Miro, Jira

  5. Flows, wireframes or experiments

    UX flows map the branching logic before any screen exists; low-fidelity wireframes let us fail fast on structure. When the open question is quantitative, we run a controlled A/B test instead.

    Tools: Miro, Figma, Frosmo

  6. High-fidelity design

    The design system goes on top of the validated structure: production UI, accessibility and interactive prototypes.

    Tools: Figma

    • Checkpoint meeting

      Design validation session

      Stakeholders walk through the final UI against the strategy and the friction points we set out to fix.

    • Checkpoint meeting

      Technical feasibility and estimation

      Design, product and engineering review the prototype together, agree constraints and break it into estimated tasks.

  7. Developer handoff and QA

    Engineers get annotated files, assets and documentation in Dev Mode covering spacing, interactions and tokens. We QA the build against the design intent.

    Tools: Figma Dev Mode

  8. Post-launch analysis

    We measure the release against the success KPIs written into the brief, find the friction that remains and iterate. Findings go into the research base, tagged for future projects.

    Tools: Looker, GA4, Airtable