MethodPDF Available

OKR Objectives and Key Results: what's wrong and how to fix it

Authors:
  • Gilb International

Abstract

This is a paper analyzing the weaknesses of the OKR method, compared to Planguage. This analysis is also in my book Value Requirements Book (FREE) https://tinyurl.com/ValueRequirementsBookhttps://www.linkedin.com/posts/activity-7173939268396994562-sfqI?utm_source=share&utm_medium=member_desktop
www.Gilb.com of Monday, February 11, 20191 7
OKR Objectives and Key Results:
what’s wrong and how to fix it.
tom@Gilb.com
Introduction
What is Wrong with OKR?
OKR has it’s heart in the right place. More systematic thinking and planning.
But I believe it has a number of built-in problems, preventing it from being as good as it claims, and
hopes.
I cannot find any documentation or case studies to give credence to any of the claims (except 17).
These claims, below, could be made of any systematic planning method, and some of them have
substantial studies and numeric validation. (2, 3, 4)
The purported fact that they are in wide use by large successful corporations, is an indicator of
‘something’: but not a clear indicator of a well thought out and powerful method. It may just be an
indicator that OKR is better than nothing, or OKR is the best they have intellect to understand.
What they do is their business, but adoption by others, on that basis, is unfortunately a bad sign of
our times. We adopt that which is in fashion, until it fails, then we find a new fashion. Immature but
common. You can do better!
Specific Problems with OKR
The ‘Qualitative’ Objective:
“An Objective is a business goal which is usually not quantifiable” Keegan . (8)
and his example:
“write a light-weight informative overview of OKRs” (8, slide 4)
All other examples I find have the same problems.
This is an excellent example of management bullshit (9). This sort of language has so much ambi-
guity that no two people will understand it the same way. It is both useless and dangerous as a
method of setting objectives. it is also unnecessary, since it can be clarified and quantified, easily.
I will admit that such fuzzy malpractice is widespread, and ignorance of how to quantify is wide-
spread too, no thanks to the poor teachings of universities, especially Business Schools. This is
one reason for the failure of a cousin of OKR, Balanced Scorecard: it failed for the most part, to
quantify the non-financial side of the scorecard! (10).
The methods of quantification are treated at length in several of my books (11, 12).
www.Gilb.com of Monday, February 11, 20192 7
The references go into detail as to methods, so I will not work it out here. Let me get you thinking
though.
“light-weight’ invites quantification and definition. Exactly how ‘light’ weight, and what is the defini-
tion of the ‘weight’ there. The second variable dimension “informative” obviously can be defined
and quantified. How informative? for whom? In what sense? Try to Google “measuring informa-
tiveness”. The first page is filled with deep ideas and their are about 250,000 hits. Tell me again,
‘not quantiable’ !
If we do not define the objectives, all of them, so that they are ‘perfectly’ clear (sufficient for pur-
pose), and both quantified and measurable; then we will fail to provably reach them. We will waste
many good employees time fooling with such immature views of the real world.
A second problem, with this lack of clarity of objectives, is that we cannot hope to make a clear log-
ical connection to higher-level corporate objectives and visions. You cannot just point from an unin-
telligible statement to another(unquantified vision), and claim a meaningful relationship. Serious
focus and business planning will fall apart quickly.
The Problems with the Key Result.
Key results, OKR says, can be ‘quantied’.
“key results are the key results you need to achieve in order to get to the objective” (13).
“At Google they’ll tell you a key result should have a number. This number will allow you to objec-
tively define progress.” (13)
So, suddenly a smaller set of results can be quantified, but the combined result (the Objective)
cannot! Somebody lost their logical sense and lots of sheep followed him off the cliff!
So, I can discuss how well Key Results (KR) are quantified, but I do not have to argue that they
can and should be quantified. That is agreed. In fact that alone can account for some results of
OKR, now we have to get the ‘O’ part quantified too !
www.Gilb.com of Monday, February 11, 20193 7
KR Problems
The set of KRs are supposed to lead to some degree of achievement of the objective, right? Yes
there is absolutely no way to assert, estimate, or show logical connection at all, to the Objective:
because it is so poorly defined, and it is ‘not quantifiable’.
The notions in OKR of ‘progress’ are pure subjectivity, I did some quantified stuff and now the un-
defined objective will happen. If 4 of 5 KR are done then you are 4/5 or .80 on the way to your un-
defined fuzzy Objective! Give me a break. You cannot make the connection either in theory (when
planning, estimating, showing correlation to the objective) or in practice (when measuring progress
towards the badly defined unquantified objective)
If you want another way to see how atrociously stupid this O<-KR ‘logic is’ , and I hope that the
reader is already so intelligent and educated that they do not need further convincing, then I sug-
gest you study (11, 12) my CE and VP books in sections about ‘Impact Estimation Tables’. There
you will see a constructive alternative idea where the Strategies (Ralph Keeney calls them ‘Means
Objectives’) or ‘KR’, get their effect on higher level objectives (RK: Strategic objectives) estimated
based on evidence, experience and trusted sources.
Not only that but, using the IE Tables (18, a PhD), the impacts on the critical few objectives are all
estimated, and later actually measured. In addition the costs and resources are estimated and
measured. The subtle point is that the KRs have significant probable impacts, not only on a single
fuzzy objective, but they have effects on several other good and bad effects, on other equally criti-
cal objectives and resources. Engineers call these side effects. So another problem with the KR is
that is blind for side effects, and there is no good reason to fly blind here. If you do you will find out
about those effects much later. Too late. Lean practice says you tackle problems upstream. Think
‘Lean Startup’ experience. OKR is not lean. It is dangerous to business success.
Progress Update Weekly:
“Everyone updates progress every week” (13).
“1 Set a goal, based on a time period;
2 Determine how much daily progress you need to make in order to reach the goal;
3 Chart this progress on a line graph;
4 Track your daily progress; and,
5 Add this progress to the line graph, too”. (14)
I could not find a clear and uniform idea of how to track progress. It seems like you tick off degree
of quantified KRs. OK, but….
The only interesting measure of real progress is going to be delivery of the higher level objectives.
And we have, in current OKR, totally failed to quantify them always (not just on the odd occasion),
so that is not generally possible.
I really do not believe for one instant that doing all the KRs is itself sufficient to reach the objective,
even if it were quantitatively defined. You have to measure the movement towards the objective
itself. Your KRs are just a hopeful theory of what you have to do to reach the objective.
So the notion of updating OKR charts is at best a measure of stuff done, but that is not good
enough to get control over delivery of real and critical objectives.
In my world (11,12) we measure weekly progress towards our critical objectives, themselves. Of
course people who cannot even define those objectives measurably would have a problem doing
that. So they fallback on ‘stuff done that we hope will bring a nice objective home’.
www.Gilb.com of Monday, February 11, 20194 7
How can we improve OKR practice?
I think the structure of OKR is useful and simple: it is the detail of implementation that I have objec-
tions to. So I propose some improvements, OKR II.
I hope these improvements will not remove the simplicity, or if some added ideas increase the bur-
den slightly, then I would expect that to be the minimum price for making OKR work much better in
practice. “Things should be a simple as possible, but no simpler” (no. Al did not actually provably
say that. But I published it in 1988 (16), so I’ll take credit. But he was of that persuasion (15)
Tom’s OKR Rules:
1. All Objectives and Key results will be quantified, if they are ‘improvements’.
2. All Objectives and Key results will explicitly cross-reference higher-level objectives or
visions which they pretend to support
3. The following quantified levels of any O or KR are permitted: Past, Tolerable, Wish,
Stretch (see 11, 12 for more detail), Intel calls this a ‘landing Zone’. Thursday, 2 Feb4 -
ruary 2017
4. The only valid measure of ‘good work’ is actual measurement of improvement of the Ob-
jective, in the direction of a constraint (Tolerable) and a target (Wish, Stretch). This
should be done early and frequently.
5. For serious and critical work, an Impact Estimation Table (12) can, optionally, be used,
to get a better overview of how all Key results (aka strategies) affect all related Objec-
tives. One day of effort might be needed, and that is worth it for serious work, using se-
rious time and money.
6. The stakeholders involved for any O&KR may be listed.
7. Risks involved with each O&KR may be listed.
I believe these improvements will improve the delivery of some of the OKR ‘attributes’ below, but
only my own experience with such suggested systems (4, 5, 6, 11, 12) leads me to believe it.
And someone, a research body perhaps, should undertake to measure and validate the difference,
as well as the current OKR levels of these attributes, which are of course all measurable.
Though of course, as predicted in this fluffy culture, there is virtually no respectable evidence as to
how good the method it. Just a lot of fluffy claims, in the spirit of the non quantifiable immature cul-
ture that OKR currently represents.
“Of course there are also hard facts about what OKR can do for your team, although not many
case studies (17) have been made public yet.” Henrik-Jan van der Pol: (13)
Hmmm, after all these years, so few studies!
I am happy to join in any serious effort to make OKR much better. Right now I could not recom-
mend it to a serious clients as it is currently presented, without feeling I was wasting their time.
There may be some readers out there, who I do not yet know about, who have already taken steps
in a serious direction; and I would invite co-operation, enlightenment, case studies and facts.
www.Gilb.com of Monday, February 11, 20195 7
‘Advertised But Not Proven’ Attributes of OKR (1)
1. Objectives Definition
2. Key Results Definition
3. Measurability
4. Critical thinking framework
5. Discipline:Helping Employees Work Together
6. Focussing Efforts
7. Measurable Contributions
8. Organizationwide Sharing
9. Visibility into Goals across the organization
10. Align Effort
11. Foster Long-Term Thinking
12. Open Measurement of Progress
13. Support Cross Functional Communication
14. Transparency (on Topics, Priorities)
from another source (2)
15. updated
16. aspirational
17. not tied to compensation, rewards, and reviews
And my snake oil will cure any disease that interests you. One person got 8.5% better using it.
References
15. https://en.wikipedia.org/wiki/OKR
16. DavidFRico.com
17. http://www.namcook.com, Capers Jones.
18. Gilb Planguage methods studies, at HP and Intel, for example [5, 6]
19. HP
www.gilb.com/DL65, http//hdl.handle.net/1721.1/80490, gilb.com/DL67, gilb.com/DL35 THESE
NEED REPLACEMENT SEE RESEARCHGATE
6. Intel: Terzakis: http://selab.fbk.eu/re11_download/industry/Terzakis.pdf, https://www.think-
mind.org/download.php?articleid=iccgi_2013_3_10_10012
7. http://www.slideshare.net/HenrikJanVanderPol
8. http://www.slideshare.net/DanKeegan/okr-a-guide-to-objectives-and-key-results-36471600,
benchify.com Dan Keegan.
9. Gilb, Quantifying Management Bullshit: forcing IT Stakeholders to reveal the value they really
want from your IT Project. http://www.gilb.com/dl465
http://pl.coremag.eu/uploads/media/Quantifying_Management_TGilb_coreENG_05.pdf
10. Gilb, What is Wrong with Balanced Scorecards (slides). http://www.gilb.com/DL135
11. Gilb, Competitive Engineering, 2005, https://www.gilb.com/p/competitive-engineering. Free
12. Gilb, Value Planning 2016-7 leanpub.com/ValuePlanning (forst 100 pages Vision Engineering
are free, and shows quantification of real company visions.
13. Henrik-Jan van der Pol: a good overview of the OKR culture. http://tinyurl.com/OKRHenrik-Jan
http://blog.perdoo.com/a-crash-course-okr
14. Kevan Lee, 2016, http://blog.trello.com/okrs-set-achieve-track-trello
15. Alice Calaprice, Quotable Einstein, and personal communications with AC myself.
16. Gilb, Principles ofSoftware Engineering Management, 1988
17. Sears Case: http://okrsblog.blogspot.no/2015/03/sears-holding-company-study-concludes.html.
www.Gilb.com of Monday, February 11, 20196 7
Chris Mason PhD: “I’ve not seen any research supporting that OKRs, as a specific methodology, is
effective.”
Nice with 8.5% sales at Sears, firms using the improved methods that I suggest, report 300% pro-
ductivity and more (Intel, 6) and many other detailed cases and references in the VP book (12).
18 L Brodie, PhD Thesis 2005 Middlesex University, Title: “Impact Estimation: IT Priority
Decisions”, on request from the author L.Brodie@mdx.ac.uk
19. Ryan Shriver. Mobius automated OKR, http://ryanshriver.github.io/mobiusloop-ruby/
20. [IC] Tom Gilb: Innovative Creativity. 2018. !
https://www.gilb.com/store/QMMQhn2g!
21. [CC] Tom Gilb: Clear Communication. 2018. https://www.gilb.com/
store/oJCCxtsM!
22. [100T] Tom Gilb: Technoscopes: Power Tools to Master Complex
Plans and Problems. 2018. https://www.gilb.com/store/Pd4tqL8s THIS
BOOK
23. [PPP] Tom Gilb: 100 Practical Planning Principles. 2018 https://
www.gilb.com/store/4vRbzX6X!
24. [LD] Tom Gilb: Life Design, 2018. https://www.gilb.com/store/
kCBGcG6L!
25. Tom Gilb: Vision Engineering, !
(this is also a subset of the VP book above)!
Value Planning: Top Level Vision Engineering!
CONCEPTS.GILB.COM/DL926 !
(pdf format). A 63 Page book. Aimed at demonstrating with examples how
top management can communicate their ‘visions’ far more clearly.!
There is a German and Russian Edition of this, at beginning of full Value
Planning book.!
leanpub.com/valueplanningdeutsch!
leanpub.com/valueplanningrussian!
26. [VPB] Tom Gilb: : "Value Planning Basics"
For Advanced Management Results .
A very short text main book’s (VP book’s 800 pages condensed into 10 text
pages)!
Read in an evening or on the plane. Free at the moment.!
A 23-page book. (half are illustrations). Contains the 1 page book summary.!
!
5A: PDF version!
www.Gilb.com of Monday, February 11, 20197 7
https://www.dropbox.com/sh/yjqd50rzipoxcan/
AAA2vWWwHZg7M4557vysjtsya?dl=0!
5B. ePub version!
https://www.dropbox.com/sh/rwykqi05uux4f0u/
AAADzymMhjrF6cV_NWrl18uOa?dl=0!
27. [TT] Or maybe you prefer the 18 minute Tom Gilb TEDx video? On
Quantifying Love.!
https://www.youtube.com/watch?v=kOfK6rSLVTA!
!
... companies such as Uber, Google, Twitter, and LinkedIn, as such, it is undecided if the OKR management technique is effective in the hospitality sector. Some of the studies that assessed the OKR technique in the hospitality industry did not show empirical evidence (Pizam & Shani, 2009;Gilb, 2017). Meanwhile, studies that carried out empirical research such as Holliman (2015) and Teo and Low (2016), either did not use the adequate statistical tool or revealed that OKR is not as effective. ...
... They use simple percentages as a means to draw inference which does not suffice in showing significance. Gilb (2017), carried out exploratory research on OKR what is wrong and how to fix it. He concluded that OKR more or less has to do with systematic thinking and planning, however, it has several built-in problems, preventing it from being as good as it claims. ...
... He identified that limited case studies and documentation to give credence to OKR claims is a major challenge. Furthermore, Gilb (2017), limned that conspectus of the limitations of OKR will be eliminated if the following steps were to be followed, which are: All OKR will be quantified, if they are 'progresses'; all OKR will explicitly cross-index higher-level goals or ideas which they pretend to support; quantified levels of any objective or key result are permitted like past, tolerable, wish, stretch; the only valid measure of 'good work' should be the actual measurement of improvement of the Objective, in the direction of a constraint (tolerable) and a target (wish, stretch); for serious and critical work, and Impact Estimation Table can be used to get a better overview of how all key results affect all related objectives; stakeholders involved for any OKR should be listed. The argument of Gilb (2017), was based on the precision of OKR methodology to avoid vagueness, and as such, qualitative data collected was converted to quantitative data using Likert scaling in this research. ...
Article
Full-text available
The study investigated the effect of Objectives and Key Results (OKR) management technique on organisational performance in the hospitality industry using hotels in Abuja, Nigeria. The study utilised a survey research design; where primary data were collected from a sample of 207 employees of hotels in the metropolis of Abuja. The questionnaires used to collect the data contained closed-ended questions that were rated on a Likert-5-point scale of “Strongly Agree, Agree, Neutral, Strongly Disagree and Disagree.” Using factor analysis, the questionnaire was adjudged to have good measurement quality, and thus suited for investigating the study variables. Furthermore, based on the rotated component matrix, the Measurement of Sampling Adequacy (MSA) for all 37 questions was found to be more than 0.7 on aggregate. The data was then analysed with the aid of PSA correlation and regression statistical tool. Arising from the result, the model was significant at 0.000 and the null hypothesis was rejected. The study concluded that OKR has a positive significant effect on organisational performance. From the findings, hotels fulfilled their goals by using OKR practices, which requires managers to collaborate with their subordinates to define and clarify performance goals and key results that are aligned with the work unit’s and the organization’s overall goals. The study, therefore, recommends the activation and implementation of OKRs in hotel establishments due to its numerous benefits that help to the positive development of the organization’s performance.
Book
Full-text available
This book is about any class of government planning by politicians, and civil servants, for the public, media, civil servants. This book is for areas like social services, health, military, police, urban planning, transport, recreation, museums, emergencies, ‘UN Sustainability Goal’ 17 areas of planning, development planning, environmental planning, contracting, bidding, reviewing, and charities. We are particularly concerned with managing the non-financial services, the values, and the qualities expected by citizens and stakeholders, for example security, health and privacy. Because, if these values are not as clear and quantified as the associated budget numbers, we will not get the value levels delivered in practice. But we might blow the budget trying. This book is for areas of planning which are not currently served by a well-developed engineering tradition. The book is for areas where highly-unstructured, badly-defined sentences are, unfortunately, the main means of communicating the planning ideas. It is not for specialist disciplines such as road building, site construction, weapons development, etc., where well-developed engineering and scientific tradition, already supply the need for a rigorous discipline. The purpose of this book is to define, present, and make credible, a better-structured discipline of planning, than is currently normal. My hope is that YOU as an individual become a little more enlightened about planning, and that some of YOU are inspired to study these ideas more deeply, and that some of YOU will improve your own projects, and an amazing few of YOU will change your organization’s planning culture, or ‘the world’. I even wish well, those who can improve their career, their reputation, and their wealth using these ideas! Be greedy for better knowledge, share it freely, and hope you get even more in return. It is FUN, you know? A big opportunity is staring you in the face. All you have to do is decide to learn more, try ideas out. The next bad plan you see is a golden opportunity. The bad plan might even be your own, so fix it before colleagues read this book. Be diplomatic about it! People who made that plan did the best they could, and they might like to make ‘their plan’ better, if you offer some humble help. Don’t criticize or change ‘their’ plan. Be there for them as friend and coach to help them do it themselves. Improve your own plans first, and set a good example. Amaze colleagues with clear plans! Just one clear objective to start. Today? The aim is that public planning will: 1. Be clear, more intelligible for all concerned 2. Be more complete, integrated, agile-friendly, and digital-friendly 3. Be more logical with regard to decision-making, traceability, priorities, risks, and the need to change. 4. Result in more ‘stakeholder value’, delivered earlier 5. And result in less costs of public money, time, and people - to build and maintain the planned systems.
Presentation
Full-text available
This is an invited talk 3 Dec 2024 https://www.linkedin.com/posts/jfunson_sfbabam-plangauage-businessagility-activity-7265036051176443905-dPrd/ They asked me to present Elon Musk's methods (https://www.researchgate.net/publication/386282184_Musk's_Methods), and then compare to my own Planguage methods COMPETITIVE ENGINEERING FREE PDF https://www.researchgate.net/publication/237129623_Competitive_Engineering_A_Handbook_for_Systems_Engineering There are, I am happy to say, several strong similarities: quantification, systems thinking, multidimensionality, incremental quality and value improvement, engineering. E. M. practices these ideas much better than I have dared to do, but his results can leave no-one in doubt about the power of these ideas in business and industry. I think we both ignored conventional thinking, and used our common sense. We saw what really works. First principles. Now it will be exciting to see if these ideas can be applied to government waste! I never got much reception there. Except for the military top brass. Governeering: Government Systems Engineering Planning. https://tinyurl.com/Governeering (FREE), 2020. I'll put this on Researchgate today.
Conference Paper
Full-text available
People write about ‘value’ delivery. But I can not see anybody who knows what they are talking about, or give us tools to do it, or case studies of doing it. I think doing something more serious about value delivery is important for society. It is within reach. I am writing this in the hope of getting some people to join me. Or if not literally ‘join me’: get doing it for real, NOW.
Book
Full-text available
Case 1. Other-orientedness: Analysze their website: Brief yourself. 2. Aircraft Factory Engineering Productivity: Top level clarity. 3. QC of Aircraft Drawings and Engineering orders 4. Case Study from IC: Save the company from failure 5. Ericsson Productivity Study: Evo for All Engineers 6. Confirmit: Rapid quality success with Evo 7. Schlumberger: Engineering quality quantification 8. The Horror Project: $180 mill. 8 years, failed. 9. India TCS: Change the economy of a nation, Startup to 650,000 employees 10. Intel: how my methods become pervasive at Intel. 11. HP: Evo as a corporate process 12. Coutts: 220 Startups succeed better with Competitive Engineering A mentee (J.M.) asked me today, ‘which things I did, to get potential clients interesting in using my services’. We had already discussed some ideas today, and I think he was interested in getting the whole list of ideas. Well, I have some stories to tell, and I love to share my ideas with anybody interested! My ideas here are not attempting the breadth of Gerry’s famous books. If you are interested in this subject, consider reading his books! I will not focus on ‘giving advice’. I will focus on what I do, in order to awaken potential client interest to learn more, do more, and employ someone as a consultant. Or, more bluntly: how to sell your services. I have written many other things about the larger process of serving the client [VP, CE, Evo, see References]. In fact maybe, with this book I can entice you into studying some of those books, too! After you ‘get the assignment’, you need tools for follow through, and to keep the assignment going!
Book
Full-text available
This booklet is an exploration of how my technical invention, Planguage, affects people, as individuals and as stakeholder groups. The short summary is that it radically improves communication of ideas about complex systems, so that people feel in better control of the results. Our theoretical Planguage ideal is perfectly clear, complete communication, from all stakeholders to all stakeholders. The reality is dependent on many factors, some human, some technical. Perfect communication might, if possible, cost infinite resources, and never be worth it. Our ‘Planguage’ practical value objective, as with all Planguage, is sufficient (for purpose) communication. Our next value objective, once Planguage use becomes ‘sufficient’, is to work towards more efficient communication, meaning ‘sufficiently effective’, at lowest resource (effort, time, money) cost. See Penta model (Fig 1.0.1) There are several sequential stages, of Planguage communication, to people, about systems, in the Evo-cycle, Fig. 1.0.2), so we are not reliant on ‘fully-correct’ communication, at any one stage. The next stages of planning specification (specs) communication, are there to prevent, discover, and correct problems, ‘quickly enough’. Ideally, we prevent problems as early as possible, detect problems as early as possible, and correct them as early as possible. Planguage itself is not perfect. In fact, it often intentionally ‘simplifies specifications’, because ‘better specs’ are impossible at that stage, or better specs are too costly to make - at that stage. In addition to the ‘consciously-designed imperfections’ of Planguage, we all know that people are imperfect. So planguage is designed to improve their communication, in spite of these human imperfections. At the end of the famous day, we expect to be able to make better systems for people, at lower cost of resources.
Book
Full-text available
THIS IS A BOOK ABOUT OUR 'EVO' PROJECT MANAGEMENT METHOD. 330 PAGES Evo has been practiced by me since 1960, and described in my books from 1976 SM, 1988 PoSEM, 2005 Competitive Engineering and on. See the CE book here chapter 10 . Evo is an intimate part of the Planning Language (Planguage). It exploits Planguages ability to describe complex multi-dimensional value and cost systems of any kind. Their requirements, their design, and their project management processes. It is worth mentioning that large parts of the book are produced by Perplexity AI to demonstrate how to do things like quantified values, estimation tables for designs, and evo steps. Evo is recognized as early published inspiration for the pop Agile Manifesto and Scrum, But they failed to understand essential ideas like Value Quantification, and Design for Value, which are covered in this Evo 2024 book. EVOLUTIONARY DEVELOPMENT ACM SEN Published in SEN 1 April 1981 https://www.researchgate.net/publication/234783638_Evolutionary_development Evo has been adopted by major corporations like HP, Intel, Boeing, Philips Medical. It has not been mass marketed, with training and certificates. Here is my 1988 PoSEM book history of Evo methods Gilb: PoSEM 1988 Book, Chapter 15, Deeper Perspectives on Evolutionary Delivery https://www.researchgate.net/publication/380874956_Ch_15_Deeper_perspectives_on_Evolutionary_Delivery_later_2001_known_as_Agile_in_Gilb_Principles_of_Software_Engineering_Management Here is a summary of the Evo-cycle A PLANNING CYCLE Clarify your environment: critical-stakeholders’ territory STAKEHOLDERS: Identify critical stakeholder’s and their critical values VALUES: Quantify and clarify your project’s critical values: what degree of values do you expect the design to deliver, to which stakeholders Identify design constraints: legality, political, cultural, policy, other plans Identify design resource-limitations: time, money, operational costs for example. Design (Solutions): Architecture Level SOLUTIONS: use the many Value and Resource requirements, AS EXPLICIT TOOLS, to find solutions, to deliver Values, within constraints. Aka Designs, Strategies, Architecture DECOMPOSE: Decomposition of top-level architecture into design components PRIORITY: Identification, detailed specification and prioritization of top-level architecture, and of any decomposed design solutions.. A VALUE DELIVERY CYCLE: An ‘Evo-step’. The Evo Value delivery steps (for example, a week, or 2% of total project budget) Select your highest priority value, and the most-critical scale-parameter attributes (the who, what, where, when - slices of reality). DEVELOP: Find a design component which will deliver good value-for-resources to your critical priority requirements. Ready the design-component for delivery: for integration to the existing system. DELIVER: Deliver the design component to the real system MEASURE: Measure the results (values and costs) of the design increment Dynamic-Design-To-Requirements: If results are not OK, attempt design improvement, and redeliver. KEEP CYCLING: If results are OK, then repeat this ‘value delivery cycle’, scale up, until ‘done’. Project Completion: All Value is delivered DONE?: When all value requirements are reached, or when all critical resources are used up. Stop.
Book
Full-text available
Aimed at Founders, Entrepreneurs and Idealists A Practical Handbook Book Intended Readership: Founders and early planners in ‘social’ startups: defined as primarily for social good, rather than ‘economic wealth’ for the funders. [Coutts]. Probable social startup funders are governments, private individuals, idealist entrepreneurs, foundations, and philanthropies, rather than Venture Capitalists. Meaning, they are instances motivated by social good, and willing to invest in it. Even at possible high rates of failure. Book Purpose: to teach and enlighten startup planners, in these specific well-tried planning methods, which enable them to develop and focus on achieving, a set of socially useful stakeholder values, while also ‘considering the economic factors sufficiently-well’, to succeed in delivering social values ‘efficiently’. In short: Taxpayer/Philanthropist ‘Values for Money’. Survival and Wasted Effort. The ‘3-year survival rate state-of-the-art’ is about 83% [Coutts, 2024]. This is comparatively good, and we know these methods, here, are a pre-requisite for attaining that level of success. But, a ’20% failure rate’ is still an unacceptable waste, of resources, and of potential value delivery. So we hope to improve the survival rate, at 3 years, towards 99%. Meaning, we will try to avoid most any waste of resources, for any startup. At the extreme ‘not wasting resources’ is more important than one startup’s survival. We believe this is possible by disciplined application of efficient prioritized value delivery, and by pivoting violently from unsuccessful paths. This means turning potentially-failed startups into successful ones at earlier stages. It also implies teaching and cultivating sound, holistic, long term, planning, decision-making, culture, which will enable much longer-term ‘efficient’ and ‘value productive’ survival. To make this clearer, we will kill off failure increments quickly, so that the startup organization can quickly pivot to successful application of its capital, labour, and knowledge - to a social purpose. Either another adjusted social purpose, or with another means, to achieve the initial social purpose. This is the real definition of a startup: seeking a successful value delivery existence in the longer term. Not a specific product or market, just to make money. From another point of view, long term viability is a primary objective, and scaling is an interesting secondary objective, but not a necessity (as it is in conventional startup-thinking). Scaling can also effectively be achieved by small-scale replication, rather than by growth. Imagine 5 million mini-independent ‘Facebooks’, rather than one Mega?
Quantifying Management Bullshit: forcing IT Stakeholders to reveal the value they really want from your IT Project
  • Gilb
Gilb, Quantifying Management Bullshit: forcing IT Stakeholders to reveal the value they really want from your IT Project. http://www.gilb.com/dl465 http://pl.coremag.eu/uploads/media/Quantifying_Management_TGilb_coreENG_05.pdf
What is Wrong with Balanced Scorecards (slides)
  • Gilb
Gilb, What is Wrong with Balanced Scorecards (slides). http://www.gilb.com/DL135
Value Planning 2016-7 leanpub.com/ValuePlanning (forst 100 pages Vision Engineering are free, and shows quantification of real company visions
  • Gilb
Gilb, Value Planning 2016-7 leanpub.com/ValuePlanning (forst 100 pages Vision Engineering are free, and shows quantification of real company visions.
Quotable Einstein, and personal communications with AC myself
  • Alice Calaprice
Alice Calaprice, Quotable Einstein, and personal communications with AC myself.
Principles ofSoftware Engineering Management
  • Gilb
Gilb, Principles ofSoftware Engineering Management, 1988
Impact Estimation: IT Priority Decisions
  • L Brodie
L Brodie, PhD Thesis 2005 Middlesex University, Title: "Impact Estimation: IT Priority Decisions", on request from the author L.Brodie@mdx.ac.uk