
How to use the "Knowns" and "Unknowns" technique to manage assumptions
Last updated: July 28, 2024 Read in fullscreen view



- 01 Oct 2020
Fail fast, learn faster with Agile methodology 695
- 08 Dec 2021
What Are The 4 Types of Maintenance Strategies? 677
- 13 May 2022
IT Training and Development: The most effective options for upskilling IT staff 635
- 02 Dec 2022
3 Levels of Quality in KANO Analysis Model 606
- 14 Oct 2021
Advantages and Disadvantages of Time and Material Contract (T&M) 577
- 19 Oct 2021
Is gold plating good or bad in project management? 521
- 03 Nov 2022
Questions and answers about Kano Model 453
- 08 Oct 2022
KPI - The New Leadership 444
- 14 Oct 2021
Stream Story - Low land stream or fast moving stream? 436
- 13 Oct 2021
What is Bug Convergence? Why is it important for User Acceptance Testing (UAT)? 399
- 23 Sep 2021
INFOGRAPHIC: Top 9 Software Outsourcing Mistakes 300
- 01 Oct 2020
Handling tight project deadlines as a business analyst 285
- 10 Dec 2023
Pain points of User Acceptance Testing (UAT) 254
- 28 Dec 2021
8 types of pricing models in software development outsourcing 252
- 19 Apr 2021
7 Most Common Time-Wasters For Software Development 250
- 11 Jan 2024
What are the Benefits and Limitations of Augmented Intelligence? 241
- 28 Oct 2023
The GOLDEN Rules of Software Engineering 240
- 13 Dec 2020
Move fast, fail fast, fail-safe 237
- 31 Oct 2021
Tips to Fail Fast With Outsourcing 228
- 05 May 2021
TIGO Magic Scale - PoC tool for you to apply dichotomous thinking before submitting RFP 222
- 06 Feb 2021
Why fail fast and learn fast? 217
- 06 Nov 2019
How to Access Software Project Size? 192
- 18 Aug 2022
What are the consequences of poor requirements with software development projects? 183
- 10 Nov 2022
Poor Code Indicators and How to Improve Your Code? 164
- 08 Jan 2024
Ask Experts: Explicitation/Implicitation and Elicitation; two commonly used but barely unraveled concepts 153
- 01 Mar 2024
(AI) Artificial Intelligence Terms Every Beginner Should Know 152
- 26 Dec 2023
Improving Meeting Effectiveness Through the Six Thinking Hats 136
- 11 Oct 2021
10 Myths About Low-End Project Management Software 133
- 17 Feb 2022
Prioritizing Software Requirements with Kano Analysis 129
- 01 Mar 2023
Bug Prioritization - What are the 5 levels of priority? 129
- 05 Jan 2024
Easy ASANA tips & tricks for you and your team 93
- 12 Mar 2024
How do you create FOMO in software prospects? 63
- 14 Mar 2024
Why should you opt for software localization from a professional agency? 51
In this post, we will show you a “Knowns” and “Unknowns” technique that quickly answers three basic questions to help you identify and manage assumptions:
- What assumptions are there that we know (validated)?
- What assumptions are there can we know but have not validated?
- What assumptions are there that we cannot know?
Knowns And Unknowns
There are four categories of information and each category consists of two words being either: “Known” or “Unknown.”
The first word states whether we have identified the data point. The second word indicates whether we can control the data point.
- Known Knowns
- Known Unknowns
- Unknown Knowns
- Unknown Unknowns
Known Knowns
Known Knowns are assumptions that have been validated and are now facts. However, it is important to note that known knowns are not necessarily static. Known knowns that could change over the course of a project — the price or lead time for a certain component — can significantly change the scope, cost, or schedule, making them important to identify and monitor as a potential risk.
Known Unknowns
Known Unknowns are assumptions that we haven’t or can’t validate. Most assumptions identified during project planning start in this category. They can be classified into three types:
- Assumptions that can become known knowns now if they are validated
- Assumptions that can become known knowns at some point in the future, but not now
- Assumptions that can’t become known knowns because we can’t control them.
The last type of known unknowns, those that can’t be controlled — flux in the price of fuel, estimated weather delays for a construction project — should be classified as risks in project planning.
Unknown Knowns
Where known knowns and known unknowns are assumptions that can be dealt with proactively — building a certain number of weather delays into the schedule — unknown knowns and unknown unknowns are issues that must be dealt with reactively.
Unknown knowns are assumptions that could have been identified as known knowns in the planning, but weren’t, and is now affecting the project. Unknown knowns occur most often as the result of poor communication. A project manager knows that a certain township reviews permit applications only once per month but fails to volunteer this information (or is not asked). The next project manager working with this township experiences the same pain point.
Unknown Unknowns
Chalk them up to Murphey’s Law. Unknown Unknowns are true surprises — a project that encounters a major delay due to a political coup in the country where the equipment is manufactured. Unknown Unknowns should be shared through lessons learned for future risk consideration for projects as a Known Unknown.
Assumptions are elemental to project management—in our language and our planning. They are often referred to as “silent assassins” because we don’t recognize them until it’s too late. The above technique provides a quick and simple approach to identify and determine which assumptions you need to focus on first. Sometimes, all it takes is a phone call or an email to get an answer. Yet, so many teams fail to take that step.
Don’t become a victim of assumptions—coach your team to see them, rate them, and resolve the assumptions they can while managing the rest as risks. It will shift team members out of daily fire-fighting into a more proactive, disciplined team as ossifications of assumptions dwindle in their frequency.