Skip to content

Hancod

Growth and product, since March 2026

How every module spec is laid out

Business goal: What the module must change for the business, in one sentence.
User stories: Who needs what and why, one story per need.
Acceptance criteria: The checks that decide “done”, written before design starts.
UAT and defects: Scenarios run against the build, every defect tracked to closure.

The same shape across FSDs, HFDs and FRDs for 12+ modules.

What ran: Functional specs, high-level and functional requirement documents for 12+ product modules, then end-to-end testing from test scenarios to defect closure.
What worked: Clearer scope and less rework between design, engineering and QA. Since June I own acquisition and conversion for a live service website, and shape what gets built next from market and customer insight.