Ship a Small First Version — Here's How to Decide What Goes In

Every project starts with a feature list that feels essential. Then you price it, and suddenly half of it has to wait. The useful skill is deciding which half — before the budget decides for you.

One question sorts most of it

For each feature ask: if this is missing on launch day, can someone still complete the main job the system exists for? If yes, it waits. A hospital system can launch without an SMS reminder module. It cannot launch without registering a patient.

Things people cut that they shouldn't

• User roles and permissions — painful to retrofit later
• Backups — cheap now, priceless the day you need them
• A basic audit trail of who changed what
• Mobile-friendly layout — most of your users are on a phone

Launch small, then let real use decide

After a month of real use you'll find that two features you were sure about get ignored, and something nobody mentioned turns out to be the daily bottleneck. That information is worth more than any planning meeting, and you only get it by shipping.