How we build

From ambiguity to buildable product direction.

A method run in production, not a values statement. Five steps move a complex product problem into a system teams can understand, sell, and ship — and every step is tied to real project proof.

Understand the system

Before anything is designed, GWSK maps the operation: users, workflows, business constraints, failure modes, and the legal, financial, or safety consequences of getting it wrong. An operator does not adopt an agent — they adopt a workflow. So the workflow becomes a shared artifact before any screen exists.

Project proof

  • NextGen AI — discovery calls and operational workflows for NDS Logistics translated into experience architectures and macro ecosystem maps.
  • Apply to Education — research recruitment automated in Python to scale outreach to 1,000+ users, testing against real candidate behaviour.

Typical artifacts

Operational mapsDiscovery synthesisFailure-mode analysisSME interviewsMacro ecosystem diagrams

Reframe the problem

GWSK separates the business problem from the product problem and names the real one. The sharp decision is usually a single sentence: the thing that, if you get it wrong, the product fails — no matter how good the demo looks.

Project proof

  • NextGen AI — reframed "build an AI platform" into "an operator must never confuse a draft agent with a live one," because that confusion is the failure mode in enterprise AI.
  • Apply to Education — reframed "redesign the forms" into "make hiring decisions auditable and accessible at public-sector scale."

Typical artifacts

Problem statementProduct thesisOpportunity framingBuild / no-build calls

Map the workflow

Before screens, GWSK maps the operational logic: who acts, what state the object is in, what decision happens next, and what needs to be auditable. The map is a shared object engineering, QA, sales, and clients all review — not a private assumption.

Project proof

  • NextGen AI — draft/production boundaries and promotion gates as auditable governance patterns, with server-confirmed states instead of optimistic UI.
  • Apply to Education — workflow redesign across candidate, admin, and union-aware HR (PIP) decision paths.

Typical artifacts

State mapsUser flowsJourney mapsMermaid diagramsPermission logicEdge-case models

Design the product system

With the workflow agreed, GWSK designs the product system: UX architecture, design systems, screens, and prototypes — with accessibility and state semantics enforced at the token level so legibility holds across every surface instead of being retrofitted per screen.

Project proof

  • Apply to Education — 10 hiring flows, an administrator management surface, and a net-new PIP product on a WCAG AA system adopted across teams.
  • NextGen AI — a WCAG AA glass design system where status is a token, not a colour choice.

Typical artifacts

UX architectureDesign systemComponent libraryAccessibility tokensPrototypesProduct screens

Package for build, demo, or decision

The output is built to be used — by engineering to ship, by sales to sell, by leadership to decide. Workflow architecture is a delivery artifact and a sales artifact at the same time. Claude and Cursor are in the workflow, so the strategy-to-handoff gap is engineered out, not narrated.

Project proof

  • NextGen AI — workflow packages tied to engineering tickets; demo storytelling and product narrative influenced $1M+ in expansion pipeline.
  • Say Yeah — a role-aware dashboard and warm-meter model packaged so trainers, learners, and admins act from one shared product surface.

Typical artifacts

Developer handoffDecision tablesDemo narrativeBuyer / investor flowRelease framingRoadmap support
Tools in the workflow

Daily Claude and Cursor in the workflow for product discovery, workflow architecture, prototyping, and engineering handoff — alongside Figma, Mermaid, and the rest of the stack.

ClaudeCursorChatGPTGeminiCopilotFigmaMermaidFireflyDescriptComfyUIQwen
Start a project

Put the method on your problem.

Most engagements start at step one: discovery. Bring the ambiguity and we'll map the system.