Artwork for podcast Impact with Digital with Jay Tikam
EPISODE 7 (Part 2): AI Strategy: The 9 Pillar AI SWIFTER Framework. A Comprehensive Guide for CEOs & Business Owners
Episode 720th May 2025 • Impact with Digital with Jay Tikam • Jay Tikam
00:00:00 00:54:28

Share Episode

Shownotes

Struggling with AI strategy? In this episode of Impact with Digital, your host Jay Tikam introduces the AI SWIFTER Framework, a 9 Pillar strategy designed to guide CEOs, business owners, and executives through successful AI implementation.

This is part two - a follow on from Part 1, where we focused on the AI Hype and noise that leaves leaders overwhelmed and confused about their next step to AI strategy, in a world where everyone is pushing them to do something - rather than do the right thing.

If you are tired of the AI hype and the fear of costly mistakes, or the fear or missing out, this episode gives you a strategic blueprint for building AI solutions that deliver real business value and has the potential to SHIFT your business to new unthinkable heights.

Jay Tikam dives into each of the 9 +1 Pillars of the AI SWIFTER Framework:

  • Alignment: Ensuring AI solves the right problem for the right people at the right time when needed in your business.
  • Innovation: Driving purposeful AI innovation within your organisation and most importantly, creating an environment for experimentation.
  • Skills: Developing the necessary skills for AI Success, & finding hidden talent that may already be lurking within your company.
  • Workflow and Adoption: Effectively integrating I into existing workflows and ensuring the solution developed is actually used and proves valuable for stakeholders.
  • Infrastructure: Building a robust AI infrastructure to cope with the demands of AI solutions.
  • Frameworks & Models: Choosing the right AI tools and techniques.
  • Tracking & Learning: Measuring AI performance for continuous improvement.
  • Ethics & Controls: Implement AI responsibly and ethically, being mindful of risks and managing reputation.
  • Results & Scale: Achieving tangible business outcomes and scaling AI solutions with repeatable modular approach that speeds up innovation and development. Ensuring the AI solution delivers enduring benefits rather than just following a latest craze.

The +1 component is present across all 9 pillars and its known as DISCOVERY. It plays a crucial role as an ongoing process for AI Strategy. Learn how to avoid AI failure and unlock the transformative potential of AI with the AI SWIFTER Framework.


Transcripts

Speaker:

If you're a business owner, a CEO, or an

executive, are you feeling the familiar

2

:

unease around all the AI hype, the sense

that you need to be doing something,

3

:

yet the fear of making the wrong

potentially costly move can be daunting.

4

:

You're not alone.

5

:

I speak with CEOs and business owners

regularly who wrestle with this exact

6

:

tension, the risk of inaction versus

the peril of going down a wrong path.

7

:

Or even complete failure

of the AI initiative.

8

:

That pressure resonates with you.

9

:

Then you, me out for the next few

minutes, because in this episode I'm

10

:

going to lay out nine fundamental pillars.

11

:

Think of them as your strategic blueprint

for navigating the complexities of

12

:

ai, allowing you to make confident,

impactful decisions, not just chase

13

:

the latest sexy trend or AI hype.

14

:

Stick with me and discover all

the nine pillars in detail because

15

:

leaving one out may just put your AI

initiative down the path to failure.

16

:

I promise you clarity and

confidence is within your reach.

17

:

Now for those of you who joined me

last time in episode six, part one,

18

:

you'll recall we took a deep dive into

the executive mindset surrounding ai.

19

:

We unpacked what internal

struggles many of you are facing.

20

:

The tug of war between the fear of being

left behind and the very real concerns

21

:

of investing down a dead end path.

22

:

We explored what failure means and

actually looks like some AI projects

23

:

seemingly succeed from a project

perspective, but fail when implemented

24

:

in the real day-to-day business.

25

:

And you'll recall that we identified

eight often overlooked factors that

26

:

can lead to AI initiatives failing

before they even truly begin.

27

:

If you happen to miss conversation.

28

:

Don't worry.

29

:

This episode stands entirely on its own.

30

:

However, if you're curious to delve

deeper into those potential pitfalls,

31

:

I'll include a link in the show notes.

32

:

But today, our focus shifts,

we're moving beyond that initial

33

:

apprehension and stepping firmly

into the path of proactive strategy.

34

:

We're transitioning from

guesswork to decision making.

35

:

To guide us, I want to introduce you to

what I call the AI swifter Framework.

36

:

Now, this isn't just another

trendy acronym to add to your list.

37

:

This is a structured approach, a

set of guiding principles designed

38

:

to bring clarity, confidence.

39

:

A clear sense of direction to your

AI journey, regardless of where

40

:

your organization currently stands.

41

:

However, before we dive into the

specifics of AI swifter, there's

42

:

a more foundational element.

43

:

We need to discuss something that

underpins every single aspect

44

:

of successfully integrating

AI into your business.

45

:

That process is called discovery.

46

:

It's the ongoing radar

that guides everything.

47

:

Think of discovery as your always

on radar in the rapidly evolving

48

:

world of artificial intelligence.

49

:

It's not a one-time task, it's an

ongoing discipline, a continuous

50

:

scanning of the horizon.

51

:

Why is this so crucial?

52

:

Because without this constant process.

53

:

Discovery.

54

:

Your AI decisions risk

becoming purely reactive.

55

:

You might find yourself chasing the

latest headlines, blindly following vendor

56

:

pitches, or even worse, being swayed

by consultants, pushing solutions that

57

:

aren't truly aligned with your needs.

58

:

Discovery provides you with a

space to observe, to thoughtfully

59

:

analyze, and to lead with a sense

of calm and informed perspective.

60

:

It eliminates the fear of missing out

because discovery provides concrete

61

:

information and turns feelings of

overwhelm into calm, reassurance, and

62

:

shows up real opportunities of ai.

63

:

Ultimately, it ensures you are

well prepared when AI genuinely

64

:

merges as as the right solution for

your unique business challenges.

65

:

All the angles to the

framework I'll cover today.

66

:

How do you implement

this discovery process?

67

:

It doesn't need to be overly complex.

68

:

Establish a simple, consistent

system for regularly scanning

69

:

industry news, keeping tabs on your

internal initiatives, monitoring

70

:

your moves, and staying abreast of.

71

:

Pay particular attention to emerging

disruptors in your market and keep

72

:

an eye on new technologies, AI

models, and emerging methodologies.

73

:

For now, simply gather this

information, file it away.

74

:

The initial goal is just

to learn and understand.

75

:

Maybe you can assign a small team

or even rotate the responsibility

76

:

to champion this discovery process.

77

:

Perhaps create a shared

document or a simple dashboard.

78

:

The key is consistency.

79

:

It needs to become an ingrained

habit within your organization.

80

:

What exactly are you looking

for in your discovering scans?

81

:

Keep an eye out on the following.

82

:

Number one, emerging

AI tools and platforms.

83

:

Number two, innovative AI-driven business

models that are gaining traction.

84

:

Number three, practical and impactful

AI use cases relevant to your industry.

85

:

Number four, the ever-evolving

ethical considerations surrounding ai.

86

:

Crucial regulatory changes

in the AI landscape.

87

:

And number six, importantly pay

attention to both the successes and the

88

:

failures of AI implementation by others.

89

:

There are valuable lessons

to be learned from both.

90

:

So what happens if you neglect this

foundational discovery process?

91

:

Quite simply, you risk

becoming a victim of hype.

92

:

You might end up investing in

systems you don't truly need.

93

:

Or worse, you live with a constant

state of mental anxiety, unsure

94

:

of what to do, who to trust, and

ultimately missing the strategic

95

:

path that's right for your business.

96

:

So who is responsible for discovery?

97

:

While everyone in organization

plays a role in being aware of d.

98

:

Designate a few passionate individuals.

99

:

Perhaps those natural enthusiasts who

love technology and digital innovation.

100

:

They can be your dedicated radar watchers.

101

:

These champions can help guide the

rest of the organization, inspire

102

:

curiosity, and foster a culture of

AI awareness within your workspace.

103

:

Discovery is what provides you

with that crucial breathing room in

104

:

the often turbulent waters of ai.

105

:

It transforms potential chaos

into confident decision making,

106

:

and it's a discipline that will

serve you exceptionally well in

107

:

every AI related conversations and

decisions you make moving forward.

108

:

You'll be informed, you'll speak with

conviction and your choices will be

109

:

rooted in objective understanding.

110

:

So, all right, now that we've

established the critical importance

111

:

of having your radar constantly

scanning, let's delve into the heart

112

:

of our discussion today, the nine

pillars of the AI Swifter framework.

113

:

Each of these pillars is intentionally

designed to help you build AI solutions

114

:

that deliver genuine sustainable

value, creating a tangible shift

115

:

into your in your business, and

potentially unlocking opportunities

116

:

you haven't even considered yet.

117

:

It's important to understand

that these pillars aren't

118

:

necessarily a linear process.

119

:

Rather, they represent the

essential foundational elements.

120

:

That should inform, inform every

AI initiative you undertake

121

:

within your organization.

122

:

So starting with the A in ai swifter

alignment at its core alignment is

123

:

about ensuring your AI efforts are

directed at solving the right problems

124

:

for the right people and in the right

way, ensuring it truly serves your

125

:

overarching business objectives.

126

:

Stakeholder needs.

127

:

Often AI initiatives are technology led,

going down a path propelled by hype,

128

:

implementing solutions not aligned with

the business goals or stakeholder needs.

129

:

The alignment component

tackles this challenge head-on.

130

:

When implemented, you are 100% certain.

131

:

That you are building, that what you are

building is needed in your organization

132

:

and is most likely to move the performance

needle if implemented correctly.

133

:

Why is this so critical?

134

:

Because AI that isn't strategically

aligned risks becoming a mere sideshow

135

:

flashy technology that doesn't

address any meaningful business

136

:

challenges or provide real value.

137

:

It's a tail waacking the dog analogy.

138

:

How is the alignment pillar implemented?

139

:

The process of alignment begins with

identifying your stakeholders and

140

:

understanding how they play their

part in your organization's ecosystem.

141

:

As I've already highlighted in previous

episodes, it's helpful to categorize

142

:

stakeholders into three key groups.

143

:

First, those you serve,

as you will remember.

144

:

Those are your shareholders, your

customers, or the communities you impact.

145

:

Second, your enablers, your

staff, your internal teams, your

146

:

partners, and the key vendors.

147

:

And third, your influences.

148

:

These are your board of directors,

regulatory bodies, and your investors.

149

:

Each shareholder group has their

unique needs and aspirations that

150

:

can be fulfilled by AI solutions,

but more importantly, you must

151

:

understand how solving problems of one

stakeholder group impacts the other

152

:

two groups that we just spoke about.

153

:

So, for example, to implement

an AI client portal.

154

:

You'd need to provide staff with

tools to upload information and

155

:

step in where AI can't provide the

information required by your clients.

156

:

Going even further, you need AI

driven performance dashboards

157

:

showing the influencers, in other

words, the executives that the

158

:

AI solution is paying off and is

positively driving business growth.

159

:

Cost reduction.

160

:

What do you need to do to get

alignment of AI solutions to

161

:

stakeholders and business needs?

162

:

You effectively understand

and achieve alignment.

163

:

You need to start with stakeholders,

categorization I just told you about.

164

:

Identify stakeholder needs through

interviews and focus groups or

165

:

surveys to gather direct insights.

166

:

Carry out stakeholder journey

mapping to visualize the experience

167

:

you are aiming to improve.

168

:

Note I said stakeholders,

not just customers.

169

:

You need to factor all three stakeholder

groups we've just covered earlier.

170

:

So map out stakeholder needs, problems

and aspirations on an impact effort matrix

171

:

to help prioritize initiatives that will

give your business the greatest results.

172

:

The most optimal investment

of time and capital.

173

:

So what if you skip this crucial

step of alignment, you might

174

:

very well end up building a

technically brilliant AI solution.

175

:

You may even build it in record

time and super efficiently

176

:

within budget estimates, however.

177

:

You will build an AI solution

that ultimately no one needs or

178

:

even worse, no one actually uses.

179

:

You'll most likely end up building

a solution looking for a problem.

180

:

It's therefore no surprise why more than

85% of AI initiatives actually fail.

181

:

Alignment is a North Star guiding your

AI led transformation based on the needs

182

:

of your business and your stakeholders.

183

:

So who's responsible for

the alignment pillar?

184

:

While your leadership team and business

analysts will likely take the lead in

185

:

this area, it's absolutely vital to

involve end users early in the process.

186

:

Listen attentively to feedback from

across your entire organization.

187

:

So let's talk about innovation.

188

:

The first I in the AI swifter

framework, in our case, innovation

189

:

isn't that shiny buzzword heavy.

190

:

Outta this world kind of innovation

that's all about being first to market.

191

:

What we're interested in here

is purposeful innovation.

192

:

Nothing groundbreaking, but

something new to your organization.

193

:

Innovation that's rooted in business

value and solves something real,

194

:

not just chasers the latest trends.

195

:

Why does this matter?

196

:

Because without a structured approach to

innovation, you're left with two extremes.

197

:

Either your businesses or you waste

time, spinning wheels on disconnected

198

:

side projects that really go nowhere.

199

:

So how do you build innovation

that actually works?

200

:

You have to start by creating

safe spaces to test ideas.

201

:

No one will want to innovate in

an environment where they get

202

:

fired for trying out new things.

203

:

Fail.

204

:

Ultimately encourage bottom up

input, not just top down vision.

205

:

Find ways to capture the ideas from

the frontline, from people who see the

206

:

opportunities and the problems while

serving stakeholders on a daily basis.

207

:

You can run small pilots with

room to fail, followed by

208

:

reflection and adaptation.

209

:

That's how you get real

insights and shift.

210

:

What could the innovation

process look like?

211

:

Remember the discovery

process I spoke about.

212

:

This is an ongoing process and it'll

give you new ideas inspired by AI led

213

:

business models and new technologies

that show you what's possible.

214

:

Discovery is the foundation to

innovation because it gives you

215

:

ideas of possibilities that you

won't even have thought about.

216

:

Don't stick to your industry.

217

:

Explore new AI technologies and business

models emerging in other industries

218

:

that has got nothing to do with yours.

219

:

So innovation starts with brainstorming

in a safe space where ideas from all

220

:

levels of the company can flow freely.

221

:

No hierarchy.

222

:

No politics and no egos.

223

:

If you're brainstorming online,

use whiteboard tools to capture

224

:

ideas from remote teams.

225

:

Make it a fun and creative process.

226

:

Remember, innovation shouldn't

just be for the sake of innovation.

227

:

You are innovating to solve a pressing

problem or delivering on the needs

228

:

of one of your stakeholder groups.

229

:

Not just customers.

230

:

Remember also that by going through

the alignment pillar, you'll be finding

231

:

innovative ways to solve a problem that

is surfaced as a priority, one that will

232

:

deliver the highest return on capital and

time invested ideas don't only come up in

233

:

well structured brainstorming sessions.

234

:

They are spontaneous.

235

:

It can come from anywhere.

236

:

Maybe when one of your team is

dealing with an irate customer.

237

:

Maybe when your employee is frustrated

by a complex and unnecessary process.

238

:

Or maybe when managers can't monitor

the performance of a business, or

239

:

maybe it comes to you as the leader

in your business when you are in.

240

:

You really need to develop a mechanism

to capture ideas where they strike.

241

:

This is in addition to the

formalized brainstorming process.

242

:

For example, keep suggestion

boxes around your office.

243

:

Develop a dedicated email

address to capture ideas from

244

:

across the organization or.

245

:

Develop a web form to capture

these innovative ideas.

246

:

Reward people that come

up with great ideas

247

:

after ideation.

248

:

The idea must translate into AI

prototypes that can be tested.

249

:

Of course, only if this makes sense

and passes the should we do it test.

250

:

Maybe you can run a design sprint around

a specific and well-defined problem.

251

:

Host internal innovation

contests like hackathons.

252

:

Alternatively, you can prototype

quickly, share the solution with real

253

:

users and listen to their feedback.

254

:

Ask them how the prototype can be

improved to make their lives better.

255

:

There are many resources and books

out there on the innovation process,

256

:

so I won't cover it here, really,

but what if you skip the step of

257

:

innovation in the AI swifter framework?

258

:

When innovation isn't guided by your

strategic objectives and stakeholder

259

:

needs, you'll end up chasing novelty

and hype instead of progress.

260

:

You pursue innovation for

innovation's sake rather than

261

:

for improving your business and

how you serve your stakeholders.

262

:

When going down the wrong type

of innovation, you burn time,

263

:

budget, and goodwill on things

that don't really move the needle.

264

:

Okay, so who should be

responsible for the process of

265

:

innovation in your organization?

266

:

Naturally, the r and d

team comes to mind, right?

267

:

If you run a small business,

you'd think it's the job of the

268

:

CEO and the other executives.

269

:

However, innovation should be

everyone's job from the front line.

270

:

To leadership because the best

ideas often come from where

271

:

the problems are felt the most.

272

:

In business, innovation

can't happen in a lab.

273

:

Ideas can come from anywhere, and

you have to have a system to capture

274

:

and quickly evaluate new ideas.

275

:

Okay, so let's now turn to S

in the AI swifter framework.

276

:

S stands for skills.

277

:

People, most people will be

forgiven for thinking that

278

:

AI is a technology challenge.

279

:

We associate AI with data methods

like large language models or buying

280

:

and deploying super fast computers

or installing internet of things,

281

:

sensors that hook up to AI systems.

282

:

But make no mistake, AI

is powered by people.

283

:

People build it.

284

:

Deploy it, question it, use it, and

clean up after it when things go wrong.

285

:

So why focus on people?

286

:

Because people make AI happen

and it's essential that you

287

:

have the right mix of skills.

288

:

You definitely need deep technical skills,

but you also need skills that motivates

289

:

and empowers humans to use the AI systems.

290

:

As you already know, this is often

referred to as change management skills.

291

:

You also need project management

skills, people who can teach others

292

:

how to use AI systems, experts who

understand risks and the ethics of ai.

293

:

Process improvement specialists,

et cetera, et cetera, et cetera.

294

:

So how do you get these skills on board?

295

:

Train up your people, staff and

executives hire new skills if you are

296

:

able to attract them in a competitive

market, outsource or bring contractors

297

:

on board to fill a temporary demand.

298

:

How do you approach the skills and people

component of the AI swifter framework?

299

:

You could start with a simple

capability map, taking stock of the

300

:

skills you already have on board.

301

:

Remember, you may have an AI

expert hobbyist working in a

302

:

completely non-AI related business

function, totally being wasted.

303

:

When considering your AI goals, you

have to find these people and make sure

304

:

they are using their skills effectively.

305

:

After all, it's a win-win.

306

:

They will be much happier in the job

while you have just acquired an AI

307

:

expert or inspiring expert without

the pain of hiring or training.

308

:

Once you know what skills you have

on board, now you can identify the

309

:

gaps, gaps, gaps based on where

you are today against what AI

310

:

initiatives will be in place in future.

311

:

This can only happen once you know what

AI solutions you are going to prioritize

312

:

and implement, and this comes from work

you've already done in the alignment and

313

:

innovation pillars we've already covered.

314

:

You'll need to figure out how to build

or acquire these skills in a market

315

:

with a demand for ai, technical and

soft skills currently outweigh supply.

316

:

Yes, this can be challenging and you

will need to find new ways to attract

317

:

top talent away from your competitors.

318

:

The Skills and People Pillar is

all about building a team that

319

:

not only understands the tech,

but also the context it lives in.

320

:

What happens if you don't develop

the skills and people pillar

321

:

of the AI Swift framework?

322

:

You may end up building

or buying a system.

323

:

No one is equipped to implement in

the business implementation stalls.

324

:

Risks escalate and the expected results

don't materialize without the right

325

:

people, it makes little sense to embark

on an ambitious AI system build things

326

:

will just come to a grinding halt until

you can get those skills on board.

327

:

In whichever way you need

to get them on board.

328

:

If you forgot everything I just told you

about skills, remember this one thing.

329

:

You may already have an AI expert in your

company that you don't even know about.

330

:

People pursuing AI qualifications

in their private life building

331

:

hobby AI projects and side hustles.

332

:

Find them and develop

an AI career for them.

333

:

So who owns the skills and people

pillar of the AI swifter framework?

334

:

Again, it's not only the

responsibility of the HR department

335

:

to find and develop AI skills.

336

:

This really is a team sport.

337

:

Anyone leading people play a role here,

whether it's HR department heads, or the

338

:

Learning and Development Department, or

its employees recommending their friends.

339

:

Possibly also their family.

340

:

Let's now turn to the W in the AI Swifter

Framework, workflows and Adoption.

341

:

This pillar is all about the use of AI

systems that are built and deployed.

342

:

It's about embedding the AI systems,

IT workflows, and adoption by users

343

:

across all stakeholder groups.

344

:

In my experience, this is often the

most overlooked part of AI initiatives.

345

:

'cause even the smartest tech in the

world is useless if no one uses it.

346

:

Executives and decision makers

often get caught up in promise of

347

:

technology thinking it'll deliver

the promised results even if the

348

:

system is right for the business.

349

:

Implemented with precision, it makes

no difference to the business if

350

:

such systems are not actually used.

351

:

So think about this.

352

:

How could an organization

end up going through the cost

353

:

and effort of implementing a

system that's not even used?

354

:

What's going on here?

355

:

This situation can easily happen

when AI initiative start with a tech.

356

:

Leaders are often mesmerized

by technology and it's promise.

357

:

You buy it and implement it, but

not because there was a need for it,

358

:

but because you believed that the

promise sold to you by the vendor.

359

:

Go back to episode one where I talked

about an AI chat, Bott example.

360

:

The bank had a predominantly

older customer base who didn't

361

:

want to use the chatbot.

362

:

They prefer speaking to a real person.

363

:

Also, in that example, when chatbots

start giving wrong answers, staff

364

:

will obviously discourage their

customers from using these chatbots.

365

:

A key missing component here is the

alignment step in our AI swifter

366

:

framework, which was ignored.

367

:

Really, the AI system implemented without

stakeholder needs assessment risks.

368

:

Why does adoption matter so much?

369

:

Because shelfware doesn't deliver

any benefits, let alone return on

370

:

investment adoption of AI systems.

371

:

In other words, AI systems that

are actually used by the target

372

:

stakeholder groups is what turns

potential and promise into performance.

373

:

So how do you get it right?

374

:

Simple focus on the alignment pillar

in the AI swifter framework, and

375

:

make sure the AI system is addressing

a genuine desire or aspiration

376

:

of a specific stakeholder group.

377

:

Then design it with a user in

mind and not for them without

378

:

any involvement from them.

379

:

You've gotta watch what people

actually do, not just what they

380

:

say they do when using a system.

381

:

Are there too many steps in

the user journey that gets

382

:

them to abandon the AI system?

383

:

Is the user interface

clunky and confusing?

384

:

Are the colors on the app

or webpage overpowering?

385

:

All of these things really do matter.

386

:

You must co-create workflows that

fit into the reality of your users.

387

:

You start with a prototype,

but then get feedback from as

388

:

many actual users as possible.

389

:

Look out for problems, listen to

their feedback and suggestions.

390

:

Ask them how the AI

solutions could be improved.

391

:

Iterate, test, get feedback, and repeat

the cycle until you get a system which

392

:

users are unanimously happy with.

393

:

Of course, you can't please everyone

and naturally some users will still

394

:

dislike certain features of workflow.

395

:

That's just part of the process.

396

:

What are some ways or

practices to ensure adoption?

397

:

Let's just explore a few

tools and techniques.

398

:

These are only examples, really.

399

:

Number one, journey mapping and testing.

400

:

Number two, shadowing

actual users on the ground.

401

:

See how they use pilot systems,

learn what works and what doesn't.

402

:

And number three, prototyping tools in

real environments with real users, not

403

:

just in boardrooms or innovation labs.

404

:

In some cases, even in the AI

system, is beneficial to the user

405

:

and co-created with their input.

406

:

Users may avoid using it deliberately

because of a fear that the AI system

407

:

is going to take away their job.

408

:

Some may just resist change

because they like doing things

409

:

either have always been done.

410

:

What if you don't focus on the workflow

and adoption pillar of the AI framework?

411

:

You won't get the intended stakeholders

using the system, a wasted investment

412

:

of time, money, and effort.

413

:

You can lose trust for the

users when a system is forced

414

:

on them without their input.

415

:

People work around systems

instead of working with it.

416

:

People resist the change, and AI

becomes just another failed project.

417

:

The who should lead this

workflow and adoption.

418

:

Ideally, you give this responsibility

to a digital transformation

419

:

lead or a change manager.

420

:

However, success depends on close

collaboration with operational leaders

421

:

to align workflows with day-to-day

realities with HR people, teams for

422

:

using training, training, change,

communication, and behavioral change.

423

:

Frontline staff for systems that

are intended to be used by customers

424

:

and other stakeholders like joint

venture partners or suppliers

425

:

IT or product managers to ensure

the technology is implemented

426

:

with usability in mind.

427

:

Change management champions in

every business unit can certainly

428

:

go a long way to encouraging

widespread adoption of the AI system.

429

:

Let's now move on to the second I in

AI swifter framework infrastructure.

430

:

This is in effect the nuts

and bolts of the AI system.

431

:

Your infrastructure is the foundation

and it includes a component

432

:

such as computer resources.

433

:

You need high performance computers that

can scale as AI technologies advance.

434

:

A more practical solution could

be to use cloud computing with

435

:

platforms like AWS Azure and Google.

436

:

They offer on demand access to vast

computer resources, which you can

437

:

scale up or down as you require

without having to invest in buying

438

:

and building the system yourself.

439

:

Many highly regulated industries will

often need to invest in their own service.

440

:

Where they can keep the data locally and

have the computer power on tap instead

441

:

of sharing it with others in the cloud,

442

:

you'll need data storage

and management solutions.

443

:

AI models learn from a vast amount

of data that need to be extracted,

444

:

cleaned, and stored in a systematic

way so that it can be retrieved easily.

445

:

Data, after all is the

lifeblood of AI systems.

446

:

Whether it's your data or external

data available in public libraries.

447

:

AI also needs high speed networks

and connectivity load as systems

448

:

need to quickly upload and download

data to perform their functions.

449

:

Such data transfers must be possible

across different types of systems.

450

:

Most importantly, the network

over which data travels.

451

:

Must be secure, protecting sensitive

data and systems against hackers.

452

:

So the AI system will need

sophisticated security and compliance

453

:

infrastructure that are kept up to date.

454

:

Why does this infrastructure

pillar matter?

455

:

Because your AI initiatives

will be limited by your infras.

456

:

If your hardware can't cope with

the demands of AI solutions,

457

:

whereas if your infrastructure

fails or doesn't function properly,

458

:

you don't get, you don't get AI

transformation, you get AI chaos.

459

:

And with AI's ability to automate

things can get out of hand very quickly.

460

:

Putting your organization, your

customers, and other stakeholders at risk.

461

:

So how do you avoid that?

462

:

You start by assessing what you

already have, what systems can

463

:

integrate, what need replacing,

what's your data quality really like?

464

:

Remember, all those gap analysis is

based on work you've already done in

465

:

the alignment and innovation pillars.

466

:

These two pillars are foundational and

they ensure you are building an AI system.

467

:

Designed to meet stakeholder needs

that shift the business to new heights.

468

:

We won't go into the technicalities

of AI infrastructure.

469

:

There's already quite a bit of

information that is already out there.

470

:

Vendors will be pleased to inform

you about the hardware so you

471

:

can get information from them.

472

:

Maybe we can dedicate a future episode

of this topic or better get some

473

:

infrastructure provider guests to go

through all the infrastructure components

474

:

and the technology stack you will need to

consider when building your AI solution.

475

:

So what's the risk if you skip

this infrastructure better?

476

:

Well, your AI system just won't work

no matter how well they're designed.

477

:

System flaws and security breaches will

expose you legally and reputationally.

478

:

So who owns the hot

infrastructure component?

479

:

Fortunately, this is one area you

don't want everyone involved, just

480

:

IT experts, your IT team, your data

architects and your cybersecurity

481

:

teams will take the lead.

482

:

If you don't have these teams, you can

outsource or bring incredible freelancers.

483

:

They're not back offers.

484

:

They're mission critical.

485

:

In this case, definitely rely on

vendors, but only once you are clear on

486

:

what AI systems you are implementing.

487

:

And most importantly why as an

executive or owner of the business,

488

:

you don't need to understand the

nuts and bolts of infrastructure.

489

:

However, you need to have a grasp.

490

:

Of the basic infrastructure needed for

AI and keep abreast of new developments.

491

:

Make sure you have a strong IT

and hardware team, whether they

492

:

are in-house or outsourced.

493

:

So next we moved the F in the AI swifter

framework, frameworks and models.

494

:

Now we're talking about the engine under

the hood, the powerhouse of AI systems.

495

:

This is where the models live.

496

:

The logic that drives your AI

talking, we are talking about

497

:

algorithms, techniques, and software

tools to build and train AI models.

498

:

It's essentially the brain of the

AI system while infrastructure

499

:

was the hardware and data.

500

:

Here we focus on the software briefly,

we've got the following AI frameworks.

501

:

Number one, machine learning

frameworks and libraries, like deep

502

:

learning frameworks like TensorFlow.

503

:

PY Torch and Kara.

504

:

Classical machine learning libraries

like T Natural Language processing

505

:

libraries like hugging face transformers,

data processing frameworks for

506

:

model preparation like Apache Spark.

507

:

The core techniques used to

learn from data by AI systems

508

:

include supervised learning.

509

:

Unsupervised learning, reinforcement

learning, computer vision

510

:

processing, and generative models.

511

:

Again, we won't delve into

the technicalities of models,

512

:

methods, and frameworks here.

513

:

Remember, this is a means to an end and

not the starting point of AI systems.

514

:

As an executive or owner of

the business, you only have

515

:

to understand basic concepts.

516

:

Keep on top of developments.

517

:

Why does this pillar matter?

518

:

For obvious reasons, the frameworks

and models component is crucial.

519

:

Think of them as sophisticated

construction kits designed

520

:

specifically for building ai.

521

:

It's like a Lego brick for building a toy.

522

:

AI frameworks can accelerate

development because of prebuilt

523

:

components, libraries and function

524

:

complex.

525

:

Make AI development more accessible.

526

:

They also ensure you are following

standardization and best practices.

527

:

AI models and methods, on the other hand,

translate data into insights and actions.

528

:

AI methods help computers learn

patterns and relationships.

529

:

They also enable generalization.

530

:

What does this mean?

531

:

The AI.

532

:

To apply learned knowledge

to novel situations.

533

:

In other words, demonstrating

intelligent behavior.

534

:

Different AI models and methods can

address different and diverse problems.

535

:

So it's crucial to choose the right model

or method for your specific problem.

536

:

Frameworks, models and methods allow

you to explain how your AI work.

537

:

If you can explain the output,

you can trust the model.

538

:

Your stakeholders can have

faith in their outputs, but how

539

:

do you choose the right model?

540

:

Pick the simplest tool

that solves the problem.

541

:

Aim for models that are testable,

auditable, and explainable.

542

:

Firstly, understand the

problem and tasks at hand.

543

:

Consider what are you trying

to achieve with the ai?

544

:

What type of data do you have?

545

:

What are the inputs and

outputs requirements?

546

:

How accurate do you need the model to

be, et cetera, et cetera, et cetera.

547

:

Then explore available model types,

like classical machine learning,

548

:

deep learning, natural language

processing, and time series models.

549

:

Once you've chosen the model,

consider what data sets are needed.

550

:

Consider how you prepare the data

and how you deal with missing data.

551

:

Then go back to the infrastructure pillar

and decide whether you have that computer

552

:

power to run these complex models.

553

:

Remember, you can buy or

rent computer power, as I've

554

:

already spoken about before,

555

:

as an executive or business owner.

556

:

You need a working knowledge

of frameworks, models,

557

:

and methods used for ai.

558

:

More importantly, you must understand

the limitations and risks because

559

:

you have an oversight responsibility

on what your team produces, whether

560

:

they're in-house or outsourced.

561

:

As a leader, you have to educate

yourself and make sure you stay

562

:

up to date on AI mechanics.

563

:

Nothing too deep here.

564

:

A high level understanding

that's all you really need.

565

:

You must ensure there are governance

mechanisms in place to evaluate

566

:

the accuracy of the models.

567

:

What's even more important is to assess

the risks of bias, transparency of the

568

:

models and maintainability, meaning

the output remains relevant over time.

569

:

The model doesn't become corrupt as

it gets more data and learns on it.

570

:

While your framework, models and

method must be smart, they must

571

:

also be ethical and responsible.

572

:

What if you choose a framework, method, or

model poorly, you will invite unintended

573

:

consequences like biases, discrimination,

and losses that your stakeholders suffer.

574

:

You can't have a brain that is corrupt or

manipulative, so I stress again, strong

575

:

governance around AI is so, so crucial.

576

:

You've got a bold challenge, mechanisms

and auditability into the AI solution.

577

:

The governance mechanism must anticipate

and quickly identify problems and weak

578

:

points and rapidly put a stop to AI system

deployment if the risk assessment fail.

579

:

Okay, so let's explore

who's involved here.

580

:

Data scientists and AI experts

naturally, but you also need to involve

581

:

wider teams like compliance officers,

legal teams, ethical working groups.

582

:

It's a cross disciplinary effort,

not a solo data science show.

583

:

Remember, the most important

controlling mechanism is.

584

:

That's going to stop disruptive AI

systems from being deployed and that

585

:

keeps check on outputs regularly,

making sure outputs are not corrupt and

586

:

don't lead to unintended consequences.

587

:

Now we come to the T in the

AI Swifter framework, the T

588

:

tracking and learning pillar.

589

:

AI isn't a launch event done and dusted.

590

:

It's a continuous improvement effort.

591

:

Success doesn't happen at a go live.

592

:

It happens over time through

learning and adaptation.

593

:

AI is developing rapidly and you as the

executive or owner and your team must

594

:

always be on a steep learning curve.

595

:

You need to know about new

developments, but you also need

596

:

to understand new regulations.

597

:

Putting guardrails on

AI system developments,

598

:

this is critical because if you

don't measure, you don't learn.

599

:

And if you don't learn, you

can't scale or course correct.

600

:

If you don't keep up with developments,

you will be outcompeted by those

601

:

that follow the latest trends.

602

:

If you don't keep up with guardrails, you

may end up on the wrong side of the law.

603

:

So

604

:

how do you build tracking and

learning into the process?

605

:

I'll define KPIs, key

performance indicators.

606

:

Track usage data.

607

:

Talk to stakeholders, watch

for outliers and edge cases.

608

:

Keep an eye on latest developments,

some tools that can help

609

:

us tracking and learning.

610

:

Include dashboards, internal audits,

surveys, and bullet database to

611

:

keep track of latest developments.

612

:

Remember that discovery is a foundational

pillar that is relevant at every

613

:

pillar of the AI swifter framework.

614

:

Use what you learn to

continuously improve.

615

:

What happens if you don't get this

tracking and learning component,

616

:

or simply you are rescaling

something that isn't working?

617

:

Or worse?

618

:

Thinking something works

when it doesn't really work.

619

:

Your AI system becomes irrelevant

over time and you lose your

620

:

competitive positioning.

621

:

You could also end up on

the wrong side of the law.

622

:

Definitely something you

don't want to get into.

623

:

The who leads this pillar?

624

:

Naturally, your analytics team

play a crucial role, but tracking

625

:

and learning must be embedded at

every level in your organization.

626

:

This is essential feedback loop making

you confident that your AI system is

627

:

always on the right path and following

cutting edge development curve.

628

:

Now we come to the penultimate

pillar e Ethics and control.

629

:

AI has power.

630

:

And the saying goes,

power needs guardrails.

631

:

I've already touched on this when

explaining other pillars, but let's zoom

632

:

in on the vital pillar of the AI swifter

framework, which is ethics and controls.

633

:

Why do ethics matter so much in ai?

634

:

'cause one ethical failure and wipe

out years of brand equity and get you

635

:

into hot waters with regulators or

face lengthy and expensive lawsuit.

636

:

Trust takes times to build

and seconds to destroy.

637

:

So how do you embed ethics?

638

:

Start with a clear ethical

framework and principles.

639

:

Define your company's core

ethical values and translate

640

:

them into ai ethical principles.

641

:

These might include fairness,

transparency, always doing the

642

:

right thing, accountability.

643

:

Privacy and security.

644

:

Develop AI ethics policies based on your

values, regulation, and best practice.

645

:

Establish an AI ethics committee or

an officer if you're a small business.

646

:

Hiring in an ex AI expert that

comes in every now and again to

647

:

make sure everything is on track.

648

:

From an ethics perspective, I've

already mentioned the importance of

649

:

a strong governance framework, which

must be developed and documented.

650

:

You need a structured approach with

clear roles and responsibilities

651

:

and decision making process for AI

development, deployment, and monitoring.

652

:

Embed ethical considerations

at every stage of the process.

653

:

Conduct regular audits and

reviews for ethical risks, biases,

654

:

unintended consequences, and

compliance with laws and policies.

655

:

So what happens if you ignore this?

656

:

You open the door to unintended

consequences that results in lawsuit,

657

:

media backlash and regulatory

heat, which I've already covered,

658

:

and who's responsible

for ethics and controls.

659

:

It's gotta be embedded in every

pillar of the AI source framework.

660

:

Assigning responsibility for.

661

:

Outcome to specific stages

and roles throughout the AI

662

:

implementation lifecycle.

663

:

Risk teams and legal and compliance

will play an important role, but

664

:

here is where leaders must step up.

665

:

They set the tone at the top, they

lead by example, and they have to have

666

:

a strong governance framework that

anticipates unintended consequences.

667

:

Surfaces them rapidly deals with

them, so that risks are minimized.

668

:

And finally, we come to the R in the AI

Swifter Framework, results and Scale.

669

:

This is where the rubber meets the road.

670

:

Proof of concept is nice, but

proof of value, that's where

671

:

real transformation begins.

672

:

If you go through all the

effort of building an AI system,

673

:

it's got to deliver real.

674

:

Tangible results, not

just today, but ongoing.

675

:

AI solutions must be sustainable.

676

:

You also want these solutions to

scale so that they give you more

677

:

return on investment over time,

results and scale is the end game

678

:

because AI has to scale to matter.

679

:

It can't stay stuck in

one pilot after another.

680

:

Remember, pilot purgatory discussed in.

681

:

So how do you scale with confidence?

682

:

Modularize your solutions.

683

:

Make sure the modules are standardized

and accessible to other teams.

684

:

Remember, build AI like Lego blocks.

685

:

Once time and effort goes into innovating

and building one component, make sure

686

:

it's available and can be used by other

teams who are building other AI solutions.

687

:

Now you can develop and deploy AI

systems fast because you don't need to

688

:

go back to the drawing board every time.

689

:

You can just take what's

working and build on it.

690

:

This gives you a huge head start.

691

:

The modules must be hosted on a

digital platform that developers

692

:

can get controlled access to.

693

:

However, document everything,

how it works, how it's deployed,

694

:

what worked, what didn't work.

695

:

Toolkits that others in

the organization can reuse.

696

:

Here are some of the practical

assets you should be developing.

697

:

Internal written playbooks, videos

that guides videos that gives guidance

698

:

on the assets and how to use it.

699

:

A digital platform with reusable

modules of code governance

700

:

frameworks for scale and oversight.

701

:

What have you skipped this?

702

:

Well, quite simply, we'll be stuck

in pilot purgatory celebrating small

703

:

wins, but never changing the game.

704

:

Who drives scale?

705

:

Again, this is everyone's responsibility.

706

:

Everyone involved has to develop

things that can be reused.

707

:

Then document what they have done to make

life easier for someone who will use the

708

:

AI related asset, develop instructional

videos and modules, delivery team, program

709

:

managers, and executive sponsors must

drive scalability in everything they do.

710

:

So that's the AI Swift framework, a

grounded, structured way to navigate

711

:

AI in your business, not just with

hype, but with real practical clarity.

712

:

We are building an AI readiness

scorecard to help you assess yourself

713

:

across the nine pillars so you know

where to start, what to strengthen,

714

:

and where the real risks are.

715

:

I include a link in the show

notes to express your interest in

716

:

completing this when it is ready.

717

:

I'm your host, Jay Tick.

718

:

This is impact with digital.

Links

Chapters

Video

More from YouTube