In my last article, I wrote about how many organizations thrive on chaos—not because it’s effective, but because leadership has failed to define priorities, roles, and processes. There’s a natural next step to that discussion: even when structure is in place, how do you know if your teams are productive? How do you prove that the organization is functioning at a high level?
That’s where great leaders distinguish themselves: they manage by fact—not assumption.
Managing by Fact Starts with the Right Metrics
You can’t manage what you don’t measure. If your understanding of team performance comes from gut feel, hallway conversations, or status meetings with no data behind them, you’re not leading—you’re guessing.
Effective leaders demand visibility into the work. They want to know:
- What’s being worked on—and by whom?
- Are projects hitting deadlines or falling behind?
- How many tickets or service requests are flowing through the team?
- What are the recurring issues?
- How often are tasks reprioritized or dropped?
This kind of insight doesn’t require a massive analytics program—it requires discipline. Whether through ticketing systems, project management tools, or weekly metrics reports, high-functioning teams know how to show their work.
You can’t improve what you can’t measure—and you can’t lead what you don’t see.
When Leadership Interrupts, There Should Be a Receipt
Too often, a top executive will declare something an urgent priority and expect IT or operations to pivot immediately. And they do. But at what cost?
If your team isn’t capturing baseline data—such as velocity, throughput, or resource allocation—it becomes impossible to measure the true impact of these top-down interruptions. A high-priority request might seem harmless until you see that:
- Two strategic projects were delayed by three weeks.
- Incident response time increased by 20%.
- A major vendor implementation had to be paused midstream.
These aren’t just anecdotes. These are facts. And they matter when it’s time to evaluate tradeoffs, resource plans, and future commitments.
Improvements Should Be Measurable
One of the biggest missed opportunities in IT and business operations is failing to measure the impact of change. When you introduce a new tool, hire additional resources, outsource a function, or reengineer a process—how do you know if it worked?
If your only feedback is “it feels better,” you’ve learned nothing.
But if you’re measuring the right things, you can show:
- Service tickets closed faster after implementing automation.
- Project backlog decreased by 30% post-reorg.
- Cost savings from consolidating vendors.
- Reduced escalations after improving a specific support process.
You can also see when a so-called improvement didn’t deliver—and course correct early.
Transparency Builds Trust
Managing by fact isn’t about micromanaging. It’s about building a culture of accountability and transparency. When everyone understands how their work is measured—and how it contributes to broader goals—they’re more likely to stay aligned, prioritize effectively, and feel ownership over outcomes.
More importantly, leaders who make decisions based on data, not anecdotes, build credibility with their teams and peers. They’re able to defend their priorities, justify resourcing decisions, and make the case for change with confidence.
The Bottom Line
If you’re not measuring your team and managing by fact, you’re not leading—you’re guessing. And in today’s fast-moving, resource-constrained world, guessing isn’t good enough.
At our next CIO Initiative Summit, I’d love to dig deeper into this topic: What does it really look like to manage IT like a business? What metrics matter? How do we build cultures where facts—not fire drills—drive action?
If you have ideas or practices you’d like to share, I invite you to reach out or bring them to the discussion. Let’s define together what it means to lead with facts—and to lead with intention.