Thread by @jstweedie

Digital transformation...oh boy do we go on about it (guilty!).

Someone said 'it's bigger than service design!'

Well, yes. But also no.

We are east to build services for peoples in Canada that are simple, easy-to-use, and trustworthy.

Also, open and transparent.

Don't forget that we wish to demonstrate evidence-based decision-making, which means using data as a strategic asset. And making (most) of that data available for others to use.i

In the buzzword bingo around digital transformation, centre on this: service design is the methodology we use to do the things (modernize a database, make a portal) to create the products and services (program delivery modes) to bring about the outcomes (open, safe, etc.) we are

Responsible for creating for people's in Canada.

Service design: method for use of inputs + activities to make products and services as outputs that result in positive outcomes for peoples in Canada.

In a nutshell.

Those of you who've already had coffee are saying 'hey, inputs, activities, outputs, outcomes - why that's a logic model! JT is talking about results chains!!!'

Indeedy I am.

And that's why product managers should ideally be program side.

Psst: IT solution architecture = program side departmental results framework

(Which used to be called the program activity architecture before it was called the program alignment architecture but which in any case makes it all pretty clear)

So digital transformation policy suite: Policy on Service and Digital + Policy on Results + Policy on Plannimg and Mamagement of Investments.