Breaking Down Your Project Into Real Milestones
How to identify the three to five milestones that matter. Most teams pick too many and lose focus.
Read ArticleSpreadsheets versus apps versus sticky notes. We tested what actually works for small teams and what's overkill. Spoiler: the answer depends on your team size.
You've got a team. Maybe it's three people, maybe it's ten. Either way, someone's asking "where are we on the deliverables?" and you don't have a quick answer. That's the moment you realize you need a system. But which one? A spreadsheet takes fifteen minutes to update and nobody checks it. An app costs money and your team won't adopt it. Sticky notes work for a week until they fall off the monitor.
The real problem isn't picking the tool. It's that most founders treat task tracking like an afterthought — something you add after you're already drowning in work. We spent the last few months talking to startup teams in Tsim Sha Tsui, Wan Chai, and Central. We looked at what they were actually using, what worked, and what they abandoned. Here's what we found.
We're not here to tell you which tool to use. We're here to tell you why each one fails in a specific way — and when it actually works.
Every startup we talked to started with a spreadsheet. Google Sheets, Excel, doesn't matter. The first week is great. Status is visible, formulas are working, everyone knows where things stand. By week three, nobody's updating it. Rows are out of date. The responsible person is busy shipping code or talking to investors. Your "single source of truth" is now three days old and nobody trusts it.
Spreadsheets work for exactly one thing: final delivery tracking. One column per person, red/yellow/green status. That's it. Use it for milestones, not daily tasks. Trying to track 40 individual tasks in a spreadsheet means you're spending 20 minutes per day just moving cells around.
Jira, Asana, Monday.com — these tools are powerful. They're also overkill for a five-person team. One founder told us: "We paid for Jira for six months. Two people used it regularly. The other three kept asking 'what's the status?' in Slack." You're paying $100+ per month and your team is still using the messaging app.
Apps work when your team is large enough to need custom workflows. When you've got separate product, design, and engineering teams who need different views of the same project. For early-stage teams, the setup time and learning curve means you'll abandon it before you get the value. The money isn't wasted on the tool. It's wasted on change management.
We watched one team manage their entire sprint with index cards on a board. Daily standups took five minutes. Everyone knew what was in progress, what was done, what was blocked. It was beautiful. Then someone moved the board to clean the wall and four cards fell on the floor. One task got lost completely.
Sticky notes work for teams in one physical location. Three to eight people. One sprint at a time. The moment you have remote people or need history ("wait, did we ship that in March?"), the system breaks. You can photograph the board, but you're still managing two sources of truth.
Pick based on your team size. Not because it's sophisticated. Because adoption depends on friction.
Use a shared document. Google Docs with a checklist. Update it at the start of the day. It takes 90 seconds. No app fees, no complexity. Your whole backlog lives in one place you both check.
Sticky notes + one shared document. Physical board for daily status, document for history and planning. You get the visual clarity of the board and the record-keeping you'll need in three months when you're hiring and onboarding new people.
Now you can afford an app. You've got enough people that custom workflows actually matter. And you're big enough that someone's job is partly keeping the system running. At this size, Jira or similar starts paying for itself.
But here's the thing nobody mentions: your system will change. The tools you pick now won't be the ones you're using in 18 months. That's okay. What matters is picking something today that your team will actually use, not something that might be perfect if everyone cooperated perfectly.
This article is informational and based on observations from real startup teams in Hong Kong. The approaches and recommendations are general guidelines. Every team's needs are different. What works for a three-person startup won't work for a ten-person team. Consider your specific situation, team preferences, and actual workflows before implementing any system. Your mileage will vary, and that's completely normal.
You don't need the best tool. You need a tool your team will actually use. Start small. A shared document and 10 minutes per day of updating. As you grow, you'll know when you've outgrown it because your team will be frustrated. That's when you move to the next thing.
The teams we talked to weren't successful because they had perfect systems. They were successful because they had consistent, simple systems that everyone understood. The tool mattered less than the habit. Build the habit first. The tool will follow.
Get in touch with questions