Skip to article
Industry perspectives

Software Products & Platforms

Build the first useful workflow before the full platform

Choose one job a user needs to finish, test its difficult cases, and make that complete before expanding the feature list.

Skar Technologies · Perspective · 3 minute read

A feature list is not a usable product

Accounts, dashboards, notifications, and integrations can all be finished while the user still cannot complete the job that brought them to the product. Planning by feature count makes this easy to miss.

Choose one specific outcome for the first release. For a service business, it might be turning a customer request into an approved appointment. Describe the beginning, the end, the people involved, and the information needed at each step. That gives every proposed feature a purpose to prove.

Test the awkward version of the job

Illustrative example—not a client result: a scheduling portal works perfectly when the customer chooses an available slot. It fails when the job needs more time, the address is incomplete, or the technician becomes unavailable.

Those cases determine whether the business can rely on the portal. A polished calendar is not enough. The workflow needs a clear status, an owner for unresolved requests, and a way to reschedule without losing the customer's information. Some exceptions can be handled manually in the first release, provided that handoff is explicit.

Learn before committing to the build

Show a simple prototype to people who actually do the work. Ask them to complete a realistic task without coaching. Watch where they hesitate, what information they look for, and what they do when the expected path is unavailable.

The GOV.UK Service Standard recommends understanding user needs and testing assumptions early to reduce the risk of building the wrong thing. Apply that discipline to the highest-risk assumption first. If customers will not supply the information needed for an estimate, improving the dashboard does not resolve the product's core uncertainty.

Define what earns the next release

For the first workflow, specify acceptance conditions: a request can be submitted, understood, assigned, completed, and recovered when something goes wrong. Include access controls and handling of sensitive information in those conditions.

Track task completion, avoidable support requests, and time spent resolving exceptions. A small sample will not establish a universal conversion rate, but observed failures can expose specific design problems.

Expand once the workflow is useful enough to operate and its limitations are understood. Keep a deferred-feature list with the evidence needed to revisit each item. The first release should demonstrate a complete outcome, not merely the outline of a larger platform.