You Know What’s Wrong With Your Technology. What Should You Fix First?
Not sure which technology problems to fix first? Learn how a Technology Direction Review prioritizes investments, risks, and decisions in three weeks.
Most organizations don’t need another person to tell them what’s wrong with their technology. They already have a list.
The ERP system is showing its age. The managed service provider wants to change the security stack. Finance is questioning software spending. Operations needs better reporting. Someone wants to move to the cloud. Someone else wants to bring IT in house. The CEO wants to know what the company is doing with AI. And somewhere in the middle of it, a business critical application is being held together by one employee who understands how it works.
None of these concerns is necessarily wrong. The problem is they’re all competing for the same money, the same people, and the same executive attention.
Leadership doesn’t need twelve more recommendations. Leadership needs to know which three decisions matter first.
A List of Problems Is Not a Strategy
Ask the people responsible for technology what needs attention and you’ll get reasonable answers. IT sees aging infrastructure and technical debt. The security provider sees vulnerabilities. The software vendor sees an opportunity to modernize. Department leaders see the systems slowing their teams down.
Each is looking at the organization through a different set of responsibilities. That is how organizations work, not a sign that anyone involved is wrong. But a pile of reasonable recommendations doesn’t add up to a reasonable technology strategy.
Take a hypothetical example. A company has an ERP system that’s genuinely difficult to maintain, with unreliable integrations and employees who complain about it constantly. Replacing it seems obvious, until leadership also has to weigh whatever else the business has in motion at the same time: a pending transaction, a team mid reorganization, a long and disruptive implementation window. None of that makes the ERP decision wrong. It changes whether now is the right time to make it.
The first question, whether the ERP needs to be replaced, can be answered by examining the technology. The second, whether replacing it now is the right call, requires understanding the business. The second question is the one leadership is actually paying to get right.
Most organizations have also already paid for an assessment. Security reports, infrastructure reviews, vendor proposals, roadmaps. Some of that work is excellent. The decisions still don’t get made, because identifying a problem and deciding what to do about it are different jobs, and an assessment usually only covers the slice it was hired to evaluate. A security assessment evaluates security. An ERP consultant evaluates the ERP. None of them is positioned to say which recommendation matters most to the business, which one should be challenged, or which one should wait. Approve five individually defensible projects without that view and the combined result can be more expensive, more complicated, and less aligned with the business than what you started with.
What a Technology Direction Review Actually Decides
A Technology Direction Review is a three week, fixed fee engagement from Coles Technical Group, built for leadership that needs to understand the environment, establish priorities, and decide what happens next.
It is not an exhaustive technical audit, a vulnerability scan, or an inventory of every device and application. It is also not a disguised sales process built to manufacture the need for an ongoing engagement.
You leave with:
- A written current state decision brief: where the organization actually stands, independent of who is reporting it.
- Technology spending and agreement review: which commitments are justified, and which are running on momentum.
- Priority risks, including which ones are being accepted instead of carried silently.
- The next three decisions, and who owns each: not a list of forty findings someone else has to interpret.
The answers don’t always produce a new project. Sometimes the recommendation is to keep the current provider. Sometimes it’s to postpone a major investment until the business is actually ready for it. Sometimes the right conclusion is that the technology is fine and the decision making structure around it is what needs to change. What the review is worth is not how many problems it finds, but whether leadership can make better decisions because of it.
Three Weeks, Three Jobs
First, the business context. Technology can’t be evaluated apart from what the organization is actually trying to do. This stage covers objectives, current technology leadership, major dependencies, spending commitments, and the recommendations already on the table, not starting from zero, but finding out what leadership already knows and where the real gaps are.
Second, the decisions get weighed against each other. A proposed investment is tested against business priorities, architecture, risk, cost, and the organization’s actual capacity to execute. A project that looks urgent in isolation might depend on a decision that hasn’t been made yet. Two initiatives might be competing for the same resources without either sponsor knowing it. A major investment might turn out to be unnecessary because the current environment, directed correctly, can already support the business.
Third, the direction gets set. Leadership gets a prioritized path, not a longer list: the next decisions, their order, their dependencies, and who owns each one. Where something needs more technical discovery before a dollar gets committed, that uncertainty is stated outright instead of papered over.
One useful question for an existing provider is: what have you recommended that leadership hasn’t approved, and why? The answer can reveal where technology recommendations have stalled, where business priorities are unclear, or where leadership has already decided the proposed investment isn’t justified. Each possibility requires a different response.
The Decision to Do Nothing Is Still a Decision
One of the most valuable things independent technology leadership can do is recommend against spending money.
That’s easy to say and hard to act on once a vendor’s put months into a proposal, a department has built expectations around a new platform, or an internal team is already committed to a direction. Momentum starts to substitute for justification, and the conversation quietly shifts from should we to how do we.
A Technology Direction Review gives leadership a chance to ask the first question before it turns into a financial commitment. If the investment holds up, you’ll know why. If it doesn’t, you’ll be in a position to say no. And if the right move is to wait, that’s a deliberate choice with a reason attached, not a decision nobody wanted to make.
What Happens After
Not every organization needs an ongoing fractional CIO or CTO. Some have solid internal leadership and just need an independent read on a handful of major decisions. Some have a strong provider but no one connecting their recommendations to business priorities. Some need architecture depth for a specific initiative. Some need standing ownership because the decisions are too frequent and too interconnected to manage one at a time.
Those are different situations, and they shouldn’t lead to the same engagement by default.
The Technology Direction Review stands on its own. You can take the direction it establishes and execute it through your existing teams and providers; nothing about it requires continuing with Coles Technical Group. Where ongoing ownership is actually needed, Technology Governance picks up from there: maintaining direction, evaluating major decisions, and holding providers accountable month to month.
Before You Approve the Next Project
Look at what’s actually competing for attention right now: the system someone wants replaced, the provider someone wants fired, the security investment waiting on approval, the application nobody trusts, the AI proposal leadership wants moving before anyone’s agreed what it’s supposed to accomplish.
If you could only approve three technology decisions in the next twelve months, which three would matter most, and who in your organization is actually accountable for answering that across the whole business, not just their own corner of it?
If that isn’t clear, the next step isn’t another technology purchase. It’s deciding what deserves the organization’s money, attention, and resources in the first place.
The Technology Direction Review is a three week, fixed fee engagement of $12,500 designed to establish those priorities and give leadership a clear direction for what happens next.
Discuss a Technology Direction Review →
Ready to find out what to fix first?
Start with a Technology Direction Review: a three week, fixed fee engagement that gives leadership a plain language decision brief and a prioritized path forward.
Discuss a Technology Direction Review