Dear friends,
There is no shortage of content about digital transformation in government.
What is much harder to find is useful guidance for people who have to make it work after the strategy deck is approved, procurement is completed, and real operational complexity begins.
That is why I created IdeasFirst.
This is a resource for leaders in Canadian provincial and municipal government who are trying to navigate information governance, records management, Enterprise Content Management, Enterprise Information Management, and the broader realities of modernization. Those terms matter. But the underlying question is simpler: how do public sector organizations manage information well enough to operate with confidence, serve people properly, and respond well when scrutiny arrives?
I’m seeing many organizations work through this question under real pressure.
They are dealing with aging systems, fragmented records, privacy and access obligations, procurement constraints, budget pressure, and rising expectations from both leadership and the public. In that environment, the challenge is not only choosing technology. It is deciding how information should be governed, connected, retained, retrieved, and used across the life of the work.
That is where I hope IdeasFirst can be useful.
What This Platform Is Trying To Do
IdeasFirst is not meant to be a vendor brochure, and it is not meant to sit at the level of abstract policy language either.
I want it to sit in the middle ground where most public sector teams actually live. That means focusing on what happens after the big decision is made. Once a platform is selected, once a modernization program is underway, once records and content start crossing SAP, shared drives, Microsoft 365, line-of-business systems, and departmental processes—what does good execution actually look like?
That implementation layer is where many projects become harder than expected.
It is also where clarity matters most.
Three Principles Behind IdeasFirst
There are three ideas that shape how I write here.
First, I care about practical implementation.
I am less interested in generic transformation language than in the operational reality that follows procurement. The difficult work usually begins when organizations need to define governance, align records practices, improve retrieval, manage retention, support audits, respond to information requests, and make systems work in a way that people will actually trust and use.
Second, I care about Canadian context.
Public sector modernization is never only technical. It is shaped by jurisdiction, legislation, procurement frameworks, accountability expectations, and the way responsibilities are distributed across ministries, municipalities, agencies, and broader public sector institutions. Advice that ignores that context may sound polished, but it usually does not travel well.
Third, I care about sub-federal public sector.
Federal initiatives often receive the most attention, but provincial and municipal organizations carry a different set of operational realities. Service delivery is closer to the ground. Information is often distributed across departments and local systems. The pressure to do more with less is constant. That deserves attention of its own.
Why My Perspective Looks The Way It Does
At OpenText, I work with Canadian public sector organizations on information governance and digital transformation challenges. That gives me a close view into the questions leaders are actually asking, and the tradeoffs they are being forced to make.
My background spans more than 20 years across IT infrastructure, cloud computing, and cybersecurity. That technical foundation still shapes how I think. It helps me understand what is happening under the hood of enterprise systems, but it also reminds me that modernization is rarely a pure technology problem.
In government especially, information problems are often operating model problems in disguise.
A records issue may also be a service issue. A retrieval issue may also be an accountability issue. A legacy-system issue may also be a policy, budget, or risk issue. So when I look at EIM, I do not see a software category first. I see a business transformation question about how institutions manage information as part of delivering public services.
That distinction matters a great deal.
What You Can Expect Here
If you spend time with IdeasFirst, you will notice a pattern.
I tend to focus on the messy middle of modernization: the place where records obligations meet business process, where enterprise platforms meet public accountability, and where information architecture either helps people do their jobs or quietly gets in their way.
Some articles will look at ECM, EIM, records management, SAP-adjacent information challenges, and digital modernization more broadly. Some will be more strategic. Some will be more operational. But the filter will stay the same: is this useful for a Canadian public sector leader trying to make a better decision in the real world?
That is the standard I want this platform to meet.
A Final Note
I know many public sector teams are being asked to modernize while carrying significant institutional complexity at the same time. That work is not simple, and it is often underestimated.
But I also think there is a real opportunity here.
Organizations that treat information governance as part of operational design, rather than as an afterthought, tend to make better decisions later. They retrieve information faster. They respond with more confidence. They reduce friction across departments. And they build a stronger foundation for modernization that lasts longer than the lifecycle of any one platform.
If IdeasFirst does its job well, it should help leaders see the work more clearly: what matters now, what can wait, where real risks sit, and what good execution actually requires.
That is the goal.
The views I express here are my own and do not necessarily reflect the official positions or strategies of OpenText.