60
Designing the Agile, Connected Organization What are we designing for? What’s the goal?

Designing the Agile Connected Organization

Embed Size (px)

Citation preview

Page 1: Designing the Agile Connected Organization

Designing the Agile, Connected OrganizationWhat are we designing for? What’s the goal?

Page 2: Designing the Agile Connected Organization

Future-Proofed Innovation

2: Org Design Model

3: Iterative Negotiated Approach

4: Experiment To Refine

1: Organizational Demands --- Context

Poss

ibilit

ies

Page 3: Designing the Agile Connected Organization

Design

Strategy

Page 4: Designing the Agile Connected Organization

4

Demands

Globalization

Augmentation/Substitution

Disintermediation

Freelancing

Education

Context

Page 5: Designing the Agile Connected Organization

5

Year Of Your Organization’s Design

Your Data – Few Are Future-Built – Looking forward to hearing back…

<2000 ≥2000 ≥2010 ≥2016 ≥201802468

1012

Participants

Page 6: Designing the Agile Connected Organization

6

Where does responsibility lie for:

Perf Man-

agement

Assignments Core Hours Meetings Vacation0

2

4

6

8

10

12

14

16

Employee Employee, Some ManagerEmployee/Team Employee/ManagerManager, Some Employee Manager

Page 7: Designing the Agile Connected Organization

7

Page 8: Designing the Agile Connected Organization

8

A 21st Century Organization, Designed in 1958

Page 9: Designing the Agile Connected Organization

9

Nucor Steel

21st Century in the 60s

Page 10: Designing the Agile Connected Organization
Page 11: Designing the Agile Connected Organization
Page 12: Designing the Agile Connected Organization
Page 13: Designing the Agile Connected Organization

13

In Your Team Room – Until 11:201. Outline one or two demands in one

of your organizations – Apply design thinking

2. Brainstorm around the issues & constraints that will play a role in whatever solution/improvement you try (don’t move to solution/improvement yet)

3. Keep your notes for the afternoon

Page 14: Designing the Agile Connected Organization

14

Page 15: Designing the Agile Connected Organization

15

In teams room working at 12:45 (Back here 1:15)How is Gore successful?How would you assess Gore and compare it to your own organization?

Creating our framework for organizational design…

Please keep notes on how you answered these two questions

Page 16: Designing the Agile Connected Organization

16

How is Gore successful?

How did you assess Gore and compare it to your own organization?

Page 17: Designing the Agile Connected Organization

17

McKinsey 7S

Page 18: Designing the Agile Connected Organization

Galbraith STAR Model

http://www.jaygalbraith.com/images/pdfs/StarModel.pdf

Page 19: Designing the Agile Connected Organization

Griffith Star Model

Context

People

Structure Technology

Process

Strategy

Page 20: Designing the Agile Connected Organization
Page 21: Designing the Agile Connected Organization

Levers Affecting Gore’s Culture

Page 22: Designing the Agile Connected Organization

People (Who they

hired)

Page 23: Designing the Agile Connected Organization

Process(Waterline)

Page 24: Designing the Agile Connected Organization

Structure:Layers of Hierarchy

Page 25: Designing the Agile Connected Organization

25

More Dimension Examples:Click to insert chart from template

Page 26: Designing the Agile Connected Organization

Process

Page 27: Designing the Agile Connected Organization

Technology

Page 28: Designing the Agile Connected Organization

Context

Page 29: Designing the Agile Connected Organization

http://www.zapposinsights.com/about/holacracy

Structure/Process

Page 30: Designing the Agile Connected Organization

The Nucor “Story” – Context/People/Structure/Process

SafetyFirst

EliminatingHierarchy

Trust&Freedom

WorkEthic

EveryoneaDecisionMaker

AllWorkersaStake

EmployeeRelations

Page 32: Designing the Agile Connected Organization

Most organizational changes do not meet their goals (they fail)

Why?

Page 33: Designing the Agile Connected Organization
Page 34: Designing the Agile Connected Organization

People

Process

TechnologyStructure

Context

0

50

100

Implement Collabora-tion Software

Page 35: Designing the Agile Connected Organization

People

Process

TechnologyStructure

Context

0

50

100

Self-Design-ing Teams

Page 36: Designing the Agile Connected Organization

Now we have a framework, let’s use it to design an organization – or a piece of one

Page 37: Designing the Agile Connected Organization

37

“Plugged-In” Management

Every Organization is DifferentHow Do Design For Your Specific Setting?

Page 38: Designing the Agile Connected Organization
Page 39: Designing the Agile Connected Organization
Page 40: Designing the Agile Connected Organization
Page 41: Designing the Agile Connected Organization

41

Page 42: Designing the Agile Connected Organization
Page 43: Designing the Agile Connected Organization

43

Stop – Look - Listen

Page 44: Designing the Agile Connected Organization
Page 45: Designing the Agile Connected Organization

AP Photo/Charles Rex Arbogast

Page 46: Designing the Agile Connected Organization
Page 47: Designing the Agile Connected Organization

Stop & Think About Your Resources: Agile,

Networks, Generations, Values, StrategyListen to Your Results: Scrum,

LeanBe Mindful

Page 48: Designing the Agile Connected Organization

Mixing

Page 49: Designing the Agile Connected Organization

Some rights reserved by advencap

Page 50: Designing the Agile Connected Organization

Levers Affecting Gore’s Culture

Page 51: Designing the Agile Connected Organization

How do you deal with the fact that we can’t do this on our own?

Page 52: Designing the Agile Connected Organization

“Negotiating” your Mix

What’s a negotiation?How do you do it?

Page 53: Designing the Agile Connected Organization

53

Stakeholders

Issues – Use the STAR to identify main levers

OutcomesValues of Outcomes to

Stakeholders

Integrative Designs as the “Deal”Iterative

Building Blocks of Negotiation

Page 54: Designing the Agile Connected Organization

54

Implementing -- Solution Stakeholder 1

Stakeholder 2

Stakeholder 3

People….: These are perceived values for the particular outcome

Outcome 1 Outcome 1 Outcome 1 Technology….. Outcome 1 Outcome 2 Outcome 3 Process….. Outcome 1 Outcome 2Outcome 3

Page 55: Designing the Agile Connected Organization

Sharing

Page 56: Designing the Agile Connected Organization

Share/Iterate

Stop-Look-Listen

Mix:Human,Technical&OrgDimensions

Evaluate

Steps to Agile, Connected Execution

Page 57: Designing the Agile Connected Organization

57

Let’s Put The Ideas Into Practice

Page 58: Designing the Agile Connected Organization

58

Stakeholders

IssuesOutcomesValues of Outcomes to

Stakeholders

Integrative Designs as the “Deal”

Plan to Negotiate To Your New Design

Page 59: Designing the Agile Connected Organization

59

Move to the first iteration of your team solution.

Graph the dimensions to mix – Deliverable

Draft Stakeholders, Issues, Outcomes, & Values -- Deliverable

In Teams:

Page 60: Designing the Agile Connected Organization

60

When You Come Back:

We’ll Share Solutions

& Implementation Ideas

(Always work in that order)