Start with the operating change
A platform should change how something works for a customer, team or business—not simply collect a list of features.
Describe the current process, the people involved, the point where it breaks and what should become easier after launch.
Bring evidence, not polished answers
Existing workflows, customer questions, spreadsheets, support messages and rough sketches are often more useful than an early visual specification.
They reveal the real language, exceptions and responsibilities the product will need to support.
Name the constraints early
Budget, timing, integrations, internal ownership and regulatory requirements shape the right solution.
Making them visible early does not limit the product. It helps the team design an achievable first version with a credible path forward.