Focused
Assessment or repair
Diagnose a problem, define an improvement path, or repair a well-bounded workflow.
How it works
From an everyday business problem to a working, reviewable result.
The process creates enough structure to reduce ambiguity without forcing every project into the same shape.
Delivery process
Four stages, with clear evidence at each one.
Small projects can move quickly. Higher-risk work receives deeper scope, validation, and release controls.
-
01
Understand the situation
Identify users, current friction, constraints, sensitive data, and the outcome that would make the work useful.
-
02
Confirm the scope
Separate required capabilities, boundaries, priorities, and assumptions in language the business can understand.
-
03
Build and review
Create the candidate experience in an isolated environment and review real workflows rather than static descriptions.
-
04
Validate and release
Check important behaviour, resolve gaps, and release through the agreed deployment process.
Engagement options
Use the smallest engagement that can solve the problem well.
A useful first step may be an assessment, a focused improvement, or a complete delivery. Scope and cost follow the work required, not a generic package.
Project
New build or redesign
Plan, design, implement, and validate a complete public website or first-party system.
Ongoing
Measured improvement
Continue improving an accepted system through agreed priorities and release controls.
What you can expect
Clear scope, visible trade-offs, and evidence before release.
The amount of ceremony changes with project risk, but the underlying disciplines remain.
- English and Chinese requirements are represented through the same structured project model.
- Unknown requirements stay visible rather than being silently discarded.
- Private destinations, credentials, and tokens are kept outside public requirements and case material.
- Important user journeys receive targeted and broader regression checks.
- New projects and revisions retain separate operation states.
First step
Describe the outcome, even if the solution is not clear yet.
A good project conversation can begin with a frustrating manual task, a weak customer journey, or a website that no longer fits.