Choose one complete workflow
Start with a frequent, understandable journey: receive an enquiry, assign an owner, clarify requirements, send a proposal and record the outcome. Identify the minimum fields and actions for every step. Avoid adding inventory, payroll or report builders simply because they may become useful. Keep such ideas in a separate backlog with their reason and intended user.
Keep essential reliability
Limited scope does not remove the need for permission checks, validation, backups and logs of critical changes. Pilot users should know which records are test data, how to correct mistakes and where to report problems. An integration required to complete the process belongs in the core scope even if technically demanding.
Define how the pilot ends
Agree pilot participants and scenarios before development. Review completed tasks and specific obstacles rather than login counts alone. Separate defects, usability improvements and new requirements afterward. Plan the next release from that feedback without changing the acceptance boundary of the existing one.
Checklist
- Provide one complete user journey.
- Test access control and data protection immediately.
- Assign pilot users and scenarios.
- Keep new ideas separate from release acceptance.
Project questions
Does an MVP need perfect design?
It needs a clear, accessible working interface. Decoration can develop later, but unreadable forms should not be deferred.