Focus on one customer group
Instead of “a platform for everyone”, decide which group’s problem you will focus on first. Users’ existing habits and the tools they use are the starting point of product conversations.
When talking to your first user, try to learn how the problem is experienced before going through a feature list.
Choose the product’s core job
Describe the main job a user can complete from start to finish in the first release. Opening and resolving a request, or creating and tracking an order, for example.
Note the extra features that don’t complete this workflow for later phases. That makes it easier to discuss the boundaries of the first release clearly.
Think about the customer structure early
Will a company have more than one user? Which information will managers access? How will customer accounts and their data be separated?
Plans, subscriptions and the usage model should also be planned around the product’s business model. These decisions affect both the screens and the technical scope.
Leave room for feedback
Decide which behaviors and feedback you will evaluate after the first release. Where users get stuck, which job they couldn’t complete and what they didn’t understand all matter.
With CM Apps you can work through the first-release scope, the customer structure and the development phases together, and evaluate new needs in later releases.