To be more successful in a development network, find better ways to produce and integrate artifacts that contribute to the goals of development. To make better hour-by-hour and day-by-day decisions, embrace a system perspective when writing more lines of code or producing more pages of documentation. Move beyond a perspective that is limited by reductionism or procrustean solutions. Encourage deliberative subtraction (deciding what not to develop) from the perspective of the system. Embrace new product development as more than a collection of diverse artifacts. Embrace new product development as more than a job characterized by obvious answers where choices are framed as ‘OR’ selections. Embrace “AND” selections that meet the needs of the present and anticipate development in the future. Facilitate set-based design over point-based design. Strive to be proficient problem solvers that also invest in future capabilities. Incorporate artifacts that contribute to the goals and minimize distractions. First rate individual contributors have the ability to hold a requisite variety of ideas about artifacts in their mind at the same time and still retain the ability to function. Refactoring F Scott Fitzgerald from The Crack-Up, April 1936 (3) With that capability, you can improve your Development Experience [DX] which is another artifact that should be made skillfully.

1. Mark A Hart, NPDP
Facts about
Artifacts:
Reimagining How New Product Development
Artifacts Impact What We Should Be Doing
Today
1

2. Outline
• Categorize artifacts
• Clarify memes
• Offer concept to
determine what individual
contributors should be
doing on a particular day
2

3. arte factum:
skill + to make
3

4. Two types of artifacts in new
product development
• External deliverables (includes
the product)
• Internal deliverables
Includes design documents, data
models, workflow diagrams, test
matrices and plans, setup scripts,…)
from Stack Exchange
4

5. • Items used to produce deliverables
• Secondary items
• Items for the future (such as training)
• Incomplete, unfinished, or abandoned
items
• Intangibles (such as strategies, tactics,
and culture)
5

6. Hour-to-hour and
day-to-day questions
• What should I be doing
now?
• Why?
• Should a specific artifact
be created?
• How much effort should
be expended creating it? 6

7. Resolving priorities
• Requests exceed network
development capacity
• Predictions about the future
• Unknown items
• Interruptions and emergence
• Flow interruptions
• Dependencies
7

8. Perspectives influence
perceptions of value
Coders value code
Copywriters value
persuasive messages
Designers value prototypes
Others value spreadsheets
8

9. “Working software over
comprehensive
documentation”
Agile Manifesto, 2001
9

10. Factors the drive perception
• Status quo
• Loudest voice
• HiPPO (Highest Paid Person’s
Option)
• Curated information
• Estimates and milestones
• Feedback from experiments
10

11. Indicators of sub-optimization
• Efforts expended to improve a
component do not improve the
system performance
• The success-limiting
component does not receive
the appropriate resources
• Rewards are silo-centric
instead of the system-centric
11

12. Producing
artifacts quickly
is not the main
objective of new
product
development
12

13. The capability to
produce artifacts
quickly contributes to
achieving the main
objectives of new
product development
13

14. Preparing individuals to make
better choices
• Improve proficiency
• Possess a variety of responses
• Requisite variety
• Consider immediate AND current
AND future timelines
• Improve interplay
• Develop implicit coordination 14

15. Preparing the development network
to make better choices
Invest to develop Einheit
15

16. Invest to improve Schwerpunkt
Preparing the development network
to make better choices
16

17. Continuously
self-correcting,
network-informed
schwerpunkt
17

18. The phrase “working
software over
comprehensive
documentation” should
not be oversimplified to
“no documentation.”
18

19. The “improvement kata (a
pattern of systematic,
scientific routine of thinking
and actions)” should not be
oversimplified to “no waste”
19

20. To be more successful in a
development network, find
better ways to produce and
integrate artifacts that
contribute to the goals of
development
20

21. To make better hour-by-hour
and day-by-day decisions:
• Embrace a system perspective when
writing more lines of code
• Move beyond perspectives limited by
reductionism and procrustean
solutions
• Encourage deliberative subtraction
• Embrace NPD as more than a collection
of diverse artifacts
21

22. • Move beyond the “OR” choices
• Embrace “AND” options
• Anticipate achieving future success
• Facilitate set-based design
• Invest in future capabilities
• Develop artifacts the contribute to goals
and minimize distractions
To make better hour-by-hour
and day-by-day decisions:
22

23. First rate individual
contributors have the ability
to hold a requisite variety of
ideas about artifacts in their
head at the same time and
still retain the ability to
function Refactoring F Scott Fitzgerald from The
Crack-Up, April 1936
23

24. Development
Experience [DX] is an
artifact that should be
made skillfully
Mark A Hart, NPDP
April 2014
24

25. Developing Winners:
Assimilating the Insights Encapsulated
in Boyd's OODA Loop
www.Developing-Winners.com
25

26. Mark A Hart
www.OpLaunch.com
Twitter: @OpLaunch
Facts about
Artifacts:Reimagining How New Product Development
Artifacts Impact What We Should Be Doing Today
10 April 2014 26