Most decisions in a growing Bangladeshi company get made on gut feel. Not because the owner doesn’t believe in data — because getting the number usually means asking someone to stop what they’re doing and build a spreadsheet, and by the time it’s ready the decision already got made without it.
“Data-driven” doesn’t mean a BI dashboard
For a 20-150 person company, being data-driven isn’t about hiring an analyst or buying a business intelligence tool. It’s three much smaller things:
- The data already exists somewhere. Attendance was recorded. Leave was approved. An expense was signed off. It’s rarely genuinely missing — it’s just trapped in whichever system captured it.
- The right person can see it without asking. If checking a number means messaging HR and waiting, that number effectively doesn’t exist for day-to-day decisions.
- It’s current, not last month’s export. A spreadsheet someone builds monthly tells you what was true a month ago. A live number tells you what’s true now, which is the only kind that’s useful before a decision, not after.
Most small companies fail on the second and third points, not the first.
The numbers worth watching day to day
You don’t need a dashboard with forty metrics. A handful of numbers, checked regularly instead of discovered in a crisis, cover most of what actually goes wrong in a growing company:
- Attendance, by department. Absenteeism in one team is usually noticed when a supervisor complains, not when the rate actually moved.
- Leave balances. If employees can’t check their own balance, every “how much leave do I have left” question becomes an HR interruption — and HR’s tally and the employee’s private tally quietly drift apart over time.
- Remaining budget, in real time. A budget being overspent is usually discovered at month end, after the commitments were already made. The useful moment to know is before approving the next one.
- Workload distribution, not just task completion. A task list tells you what’s done. It doesn’t tell you that one person on the team is quietly carrying three-quarters of the work — something that’s invisible until that person takes leave and everything slows down.
- Whether a review cycle actually finished. A performance rating distribution only means something if the cycle completed. If a third of managers never submitted reviews, the “average rating” is really just describing the managers who did their paperwork.
Where the spreadsheet approach breaks down
A monthly reporting spreadsheet works fine right up until the person who built it goes on leave, changes a formula by accident, or leaves the company — and then nobody fully trusts the numbers again, including the person who inherits it.
This is the pattern behind most “we should really track this better” conversations: the data existed the whole time, but the path from record to decision ran through one person’s manual process, and manual processes have a single point of failure.
Start with three numbers, not a system
You don’t need to solve reporting company-wide in one go. Pick three numbers that would actually change a decision if they moved — not numbers that are interesting, numbers that are actionable — and make sure the person who needs them can see them without asking anyone. Attendance rate for the team with the highest turnover risk. Remaining budget for the department that always runs close to the line. Workload distribution for the team that’s been “fine” for six months straight.
Everything past those three is easier to add once the first three are actually working.
This is exactly why Utso treats reporting as something that comes with the modules you already use rather than a separate product bolted on afterward: attendance dashboards, live leave balances, real-time budget tracking, workload analysis, and performance-cycle completion, all reading from the same records the rest of the platform already produces. The HR analytics page has the detail on exactly what’s available today.
This article is about the questions worth asking regularly, not a specific product feature list. What Utso currently reports on is documented on the HR analytics page linked above — check there for the exact, current scope rather than assuming.