Fri, 9 May, 2025
How I carry out work
“From one person’s problem to everyone’s solution.”
I believe design isn’t magic—it’s methodical, empathetic problem-solving. Here’s my five-step framework that transforms rough ideas into thriving digital products. Expect continuous collaboration, quick iteration, and real-world validation. If you’re after hype without substance, this isn’t for you. But if you want measurable impact and human-centered innovation, let’s dig in.
Intention (Find the Real Problem):
Why It Matters: Products flop when we solve the wrong problems. I observe how people are currently coping with an issue, gather relevant metrics, and define a clear goal. In Practice: Interviews, quick prototypes, or even anecdotal data—whatever it takes to confirm there’s a genuine need.
Internalisation (Absorb & Align):
Why It Matters: High-level understanding means less guesswork. I sync with your team, business objectives, and user feedback to unify everyone’s vision. In Practice: I’ll map user journeys, create user stories, and highlight must-have features—so we tackle the root cause, not just symptoms.
Actualisation (Prototype Rapidly):
Why It Matters: Early, tangible models prevent expensive missteps. We quickly prototype concepts and run them by real people to see if we’re on the right track. In Practice: Fast design sprints, user tests, and iteration loops until our concept gains real traction.
Execution (Build & Launch):
Why It Matters: Polished products that serve actual needs are more likely to succeed. I collaborate closely with developers, PMs, and stakeholders, ensuring seamless design-to-development handoff and consistent branding. In Practice: Cohesive design systems, agile sprints, and continuous feedback cycles that keep the product user-focused and dev-friendly.
Expansion (Grow the Impact):
Why It Matters: Once you have a validated core product, scaling strategically can amplify ROI and user satisfaction. In Practice: We refine features based on usage data, add new services, and scale our approach to new markets or segments—always maintain the human-centric backbone.
When you solve a real problem for one user, you learn how to solve it for thousands more—without watering down the solution.
Filed under:
Methodology