What Should Actually Happen in a Quarterly Technology Review?

If your quarterly technology review consists of someone showing you how many support tickets your employees opened, you probably aren't getting much value from the meeting.

Ticket volume can be useful operational information.

But it isn't a technology strategy.

A good technology review should create a regular opportunity to step away from day-to-day support and look at the bigger picture.

Start with the business

Technology shouldn't be reviewed in isolation.

The conversation should begin with what is happening in the organization.

Are you hiring?

Opening or closing a location?

Adding a new service?

Changing software?

Working with larger customers?

Facing new contractual or regulatory requirements?

Trying to reduce costs?

Planning an acquisition?

Changes in the business often create technology needs before anyone opens a support ticket.

Understanding those changes gives your IT provider a chance to plan with you instead of reacting afterward.

Review the risks that matter

Not every technical problem deserves the same amount of attention.

A useful technology review should identify the risks that actually matter to the business and put them in perspective.

That might include an aging server, an unsupported computer, a recurring security issue, a recovery-plan weakness, or a technology vendor the company relies on heavily.

The point isn't to create a giant list of everything that could possibly go wrong.

It's to answer:

What are the most important things we should know about right now?

What should we do about them?

And what can reasonably wait?

Look at the health of the environment

This is where some technical information belongs.

Are devices being maintained properly?

Are security tools operating as expected?

Are important systems nearing end of life?

Are backups and recovery systems healthy?

Are there recurring support issues that suggest an underlying problem?

Has the environment drifted away from established security practices?

Leadership doesn't need every technical detail.

It needs enough information to understand the condition of the environment and make decisions.

Talk about the roadmap

One of the most valuable outputs from a technology review is a forward-looking plan.

What equipment should be replaced over the next year?

What projects are approaching?

Are there security improvements that should be prioritized?

Does the organization need to budget for licensing, hardware, connectivity, or another technology investment?

A roadmap allows those expenses to become planned business decisions rather than surprises.

Review what was previously decided

A strategy meeting isn't useful if every quarter begins from scratch.

The group should revisit earlier decisions and action items.

What did we agree to do?

What was completed?

What is still outstanding?

Did something change that affects the priority?

Should a previously identified risk now be accepted instead of fixed?

That creates accountability on both sides of the relationship.

A technology review shouldn't be a sales meeting

There will be times when the right answer involves buying something.

But if every conversation somehow ends with a new product recommendation, the review isn't serving its purpose.

Sometimes the right recommendation is to replace something.

Sometimes it's to change a process.

Sometimes it's to investigate further.

Sometimes it's to do nothing right now.

A trusted technology advisor should be comfortable with all four answers.

You should leave knowing what's next

At the end of a useful technology review, leadership should understand:

The most important technology risks.

The decisions that need to be made.

The projects coming next.

The likely budget impact.

Who owns each next step.

That is far more useful than knowing your company opened 47 tickets last quarter.

Support keeps today's technology working.

Technology reviews help make sure tomorrow's technology is headed in the right direction.