39
KISKO LABS OY | PRESENTATION 1 Conceptualization in Software Development Lauri Jutila, Kisko Labs Oy, 6.9.2011

Conceptualization in Software Development

Embed Size (px)

DESCRIPTION

Lecture at HAAGA-HELIA about conceptualization in software development. A deck of stories about conceptualization, prototyping and design themes that influence software development at Kisko Labs.

Citation preview

Page 1: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 1

Conceptualization inSoftware Development

Lauri Jutila, Kisko Labs Oy, 6.9.2011

Page 2: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 2

L A B S

Page 3: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Conceptualization

3

Page 4: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

A concept (substantive term: conception) is a cognitive unit of meaning — an abstract idea or a mental symbol sometimes defined as a "unit of knowledge," built from other units which act as a concept's characteristics.

4

Page 5: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

conceptualize - To form a concept or concepts of, and especially to interpret in a conceptual way

5

Page 6: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

We Live InA Creative Society

6

Page 7: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Age of AgricultureIndustrial Age

Age of Information IntensificationAge of Creation Intensification

Murikami Teriyuasu, Nomura Research Institute

7

Page 8: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Agriculture Age (farmers)

Industrial Age (factory workers)

Information Age (knowledge workers)

Conceptual Age(creators & emphatizers)

Daniel Pink, A Whole New Mind

8

Page 9: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“Get into the ‘Dream Business’... the ‘Incredible Imaginings’

Business.”Tom Peters

9

Page 10: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 10

Technology

Business Design

Page 11: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Future of Software Development

11

Page 12: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 12

Software is no longerplanned and built. Software is

envisioned and evolved.

Page 13: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 13

Projects start with a vision followed shortly by the first iteration, not with architecture, plans and specifications.

Page 14: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

The product, the architecture, the plans and the specifications evolve as the team adapts to a ever-unfolding reality of the market and the technology

14

Page 15: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

The Power of Prototypes

15

Page 16: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“Not all Hollywood movies are hits, but very few are bombs. They’re usually saved from that ignominious fate by the use of prototypes - scripts and storyboards. The script is the prototype for the story, and the storyboard is the prototype for production.”

16

Page 17: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“Any major problems with the movie can be corrected at the prototype stage, long before much money is spent. ... What makes prototypes so powerful, ... is that they provide a ‘near life’ experience for the collaborators. Everyone on the team ... can immediately see whether the concept will work in the real world.”

17

Page 18: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“Prototypes can also cut through the ‘red tape’. Instead of starting with a list of features and working toward a concept, team members can go straight to a concept, then add whatever features are needed to support it. And if the concept looks like a loser? Hey -- it’s just a concept -- start over with a new one.”

18

Marty Neumeier, Brand Gap

Page 19: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 19

Photo by Ryan Wang

Page 20: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“We made mistakes, of course. Most of them were omissions we didn’t think of when we initially wrote the software. We fixed them by doing it over and over, again and again.”

20

Page 21: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“We do the same today. While our competitors are still sucking their thumbs trying to make the design perfect, we’re already on prototype version #5”

21

Page 22: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“By the time our rivals are ready with screws and wires, we’re on version #10. It gets back to planning versus acting: We act from day one; others plan how to plan — for months.”

Bloomberg on Bloomberg

22

Page 23: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“The best way to have good ideas is to have lots of ideas.”

Linus Pauling

23

Page 24: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION 24

Photo by Photomatt28

Page 25: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

The way to make a better aircraft wasn’t to sit around perfecting a design, it was to get something up in the air and see what happens, then try to fix whatever goes wrong.

Eric Abrahamson & David Freedman, Chapter 8, “Messy Leadership,” from A Perfect Mess: The Hidden Benefits of Disorder

25

Page 26: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Lessons from Taiichi Ohno

26

Page 27: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

現地現物(Genchi Gembutsu)

“Go and see for yourself” or “go and see”

27

Fingerspitzengefuhl

Page 28: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

改善(kaizen)

“Improvement”

28

Page 29: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

自働化(jidoka)

ji = "auto”, do = “motion”, ka = “-ation”

29

Page 30: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Experience Economy

30

Page 31: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Experiences are as distinct from services as services are

from goods.Joe Pine & Jim Gilmore

The Experience Economy: Work Is Theatre & Every Business a Stage

31

Page 32: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

ScintillatingEXPERIENCES

ServicesGoods

Raw Materials

32

Page 33: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

CUSTOMER SUCCESSScintillating EXPERIENCES

ServicesGoods

Raw Materials

33

Page 34: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“ ‘Results’ are measured by the success of all those who have

purchased your product or service”

Jan Gunnarsson & Olle Blohm, The Welcoming Leader

34

Page 35: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

Designful Software

35

Page 36: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

HYPOTHESIS:

DESIGN is theprincipal difference

between love and hate!Tom Peters

36

Page 37: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“At Sony we assume that all products of our competitors have basically the same technology, price, performance and features.

Design is the only thing that differentiates one product from another in the marketplace.”

Norio Ohga

37

Page 38: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“To grow, companies need to break out of a vicious cycle of competitive benchmarking and

imitation.”— W. Chan Kim & Renée Mauborgne, “Think for Yourself —

Stop Copying a Rival,” Financial Times

38

Page 39: Conceptualization in Software Development

KISKO LABS OY | PRESENTATION

“You can’t be a serious innovator unless and until you are ready,

willing and able to seriously play. ‘Serious play’ is not an oxymoron; it is the essence of innovation.”

Michael Schrage, Serious Play

39