Technology Strategy
Your business has a plan. Does your technology?
Growth changes things.
New locations. New employees. New systems. Acquisitions. New customer expectations. More data. More vendors. More security concerns. More complexity.
Along the way, technology decisions get made one at a time. A new application here. An infrastructure upgrade there. Another vendor. Another integration.
Each decision may make sense on its own.
The question is whether they all add up to where the business is going.
Marshall Technology helps leadership build a practical technology strategy around the business you are becoming, not just the technology you have today.
At some point, individual technology decisions become a strategy problem.
Most companies don’t wake up one morning and decide they need a technology strategy.
Something usually causes the conversation.
- We’re growing. Can our current technology keep up?
- We’re acquiring a company. How are we going to bring two technology environments together?
- We’re replacing a major business system. What else does that decision affect?
- We have too many systems doing similar things. Which ones should we keep?
- Our infrastructure is aging. What should we modernize first?
- We have more technology projects than budget. Which ones actually matter?
- We know AI is going to affect our business. How does it fit with everything else we’re already doing?
These may look like separate problems.
Often, they’re not.
They’re technology decisions that need to be made in the context of the business.
Technology strategy starts with where your business is going, not with what technology you already have.
Before talking about products, platforms or projects, we need to understand the business.
Where are you trying to grow? Are you adding locations, employees, services or customers? Are acquisitions part of the plan? Where are operations struggling today? What needs to become easier or more scalable? What information does leadership need that it can’t easily get? What major investments or changes are already coming?
What will the business need to be able to do tomorrow that it can’t do well today?
That’s where the strategy starts.
Then we look at what has to support it.
Technology doesn’t operate in separate boxes.
- Applications depend on data.
- People depend on infrastructure.
- Reporting depends on systems working together.
- Security depends on identity, applications, infrastructure, vendors and people.
A decision in one area can create consequences somewhere else.
That may involve business applications and data, infrastructure and architecture, security and resilience, vendors and investment, or the technology implications of growth and organizational change.
The point isn’t to develop a separate strategy for every part of the technology environment.
It’s to understand how the pieces fit together before making decisions that affect the business for years.
When the business changes, technology has to move with it.
Acquisitions, divestitures and other major business changes compress a lot of technology decisions into a short period of time.
Two organizations may suddenly have different email platforms, payroll systems, accounting systems, networks, vendors, security standards and ways of operating.
Now decisions have to be made.
- Which systems become the standard?
- What gets migrated or consolidated?
- What needs to stay separate?
- How will users, identities and data move?
- Which contracts continue?
- What needs to work on Day 1, and what can wait?
A divestiture or carve-out creates many of the same questions in reverse.
And through all of it, the business still has to operate.
The technical migration may be the visible project. The strategy is everything that has to be decided around it.
Marshall Technology brings practical experience from technology integrations, migrations, divestitures and carve-outs, including transitions involving payroll, accounting systems, business applications, infrastructure and email platforms.
The work has to be sequenced around the business, its people and its operations so the company can keep moving while the technology changes around it.
Knowing when to change matters just as much as knowing what to change.
- Not every old system needs to be replaced.
- Not every manual process needs a new application.
- Not every workload belongs in the cloud.
- Not every problem needs AI.
- And not every good technology project needs to happen this year.
Sometimes the right decision is to keep what you have. Sometimes it’s to simplify or consolidate. Sometimes additional investment is warranted. And sometimes a good idea should wait because something more important needs to happen first.
Technology strategy is knowing when what got you here won’t get you where you’re going.
And making the change before it becomes a business problem.
A strategy should help you make decisions.
A technology strategy should make decisions easier, not create another document leadership has to interpret.
It should help leadership decide what stays, what changes, where to simplify, where to invest and what can wait.
It should also identify the decisions that aren’t ready to be made.
“We don’t know yet” can be a perfectly good strategic answer.
Maybe there isn’t enough information. Maybe two platforms need further evaluation. Maybe the cost of changing isn’t understood yet. Maybe the business itself hasn’t made a decision that technology depends on.
Good strategy doesn’t manufacture certainty.
It identifies what needs to be learned, who needs to make the decision and what happens next.
Business Direction → Technology Decisions → Technology Roadmap
Understand where the business is going.
Understand enough about the current technology environment to know what can support that direction and what can’t.
Make the important decisions.
Then turn those decisions into a practical roadmap for what happens now, what happens next and what can wait.
The roadmap should be useful enough to guide real investment and execution, not just describe an ideal future.
You leave with a plan.
The exact scope depends on the business and the questions we’re trying to answer, but a Technology Strategy engagement is built around four practical outputs.
Executive Technology Strategy
A plain-English explanation of where technology needs to go, why it needs to go there and how that direction supports the business.
Current State & Future Direction
The important applications, infrastructure, data, vendors, dependencies and constraints affecting the strategy today, along with a practical view of how the environment should evolve.
Strategic Decisions & Investment
Clear direction around what should stay, change, consolidate, integrate or receive additional investment, along with the major budget, sourcing and governance considerations behind those decisions.
Prioritized Technology Roadmap
A practical sequence of initiatives showing what should happen now, next and later, including major dependencies, ownership and investment considerations.
Technology stops being something the business reacts to and becomes something the business plans for.
I’ve spent my career making these decisions from inside the business.
Technology strategy looks different when you’re responsible for living with the decisions afterward.
I’ve spent decades leading technology in growing, multi-site organizations and working directly with executive and operational leadership as those businesses changed.
I’ve managed technology through acquisitions, integrations, divestitures and carve-outs; major payroll, accounting, business application and email platform transitions; data center moves; server and architecture changes; building-wide Wi-Fi deployments; and the evolution of wide-area networks from frame relay to MPLS to SD-WAN.
Those weren’t technology projects happening in isolation. They were business decisions involving cost, timing, operations, risk, vendors, people and what the organization would need next.
Some technology decisions worked for years.
Eventually, some of those same decisions had to change because the business changed.
The technologies changed. The job didn’t.
Understand where the business is going. Understand what the current environment can and can’t support. Make good decisions about what comes next. Build a realistic plan to get there.
That’s the perspective Marshall Technology brings to Technology Strategy.
Where do you start?
That depends on the question you’re trying to answer.
Don’t have a clear picture of your technology environment?
An IT Health Check can establish what you have, what’s working, where you’re exposed and what needs attention.
Know where the business is going but don’t have a technology plan to support it?
Technology Strategy is a defined engagement that connects the business plan to the technology decisions, investments and roadmap required to get there.
Have the direction, but need someone to own it and keep it moving?
Fractional IT Leadership provides ongoing technology leadership across internal IT, vendors, projects, budgets, risk and business priorities.
Technology Strategy produces the direction and roadmap. Fractional IT Leadership provides ongoing leadership to own that direction and keep it moving.
Understand where you are. Decide where you’re going. Then make sure someone owns getting you there.
Where is your business going next?
If you’re growing, acquiring, consolidating, replacing major systems, modernizing infrastructure or simply facing more technology decisions than you have a strategy for, let’s talk.
You don’t need to know what the technology answer is yet.
That’s the point of the conversation.