How Do We Avoid Perfectionism and Still Manage Quality? - DBR 019
Episode 19 of the Do Busy Right - The Task and Attention Management Podcast podcast, hosted by Larry Tribble, Ph.D., titled "How Do We Avoid Perfectionism and Still Manage Quality? - DBR 019" was published on February 23, 2024 and runs 54 minutes.
February 23, 2024 ·54m · Do Busy Right - The Task and Attention Management Podcast
Episode Description
- Only you, as the knowledge worker, can know what you are trying to say or deliver
- Example: delivering truth when it's bad news
- An outcome
- Quality is like school exams (at least some of the time)
- If we have an objective external standard
- Where does production quality fit in?
- 'production quality' above a certain threshold is not a measure of quality
- Unless it is. Entertainment seems to have this property.
- Kinds of flaws in knowledge work (expand here)
- Factual Knowledge – what are the facts, what do we know? E.g. diagnosis
- Process Knowledge – next action that should be taken, E.g. treatment regiments and delivery
- Understanding Knowledge – what is our strategy, changes to standard procedure e.g. when treatment doesn't work
- Knowledge Creation – new knowledge/processes/workflows – Insight e.g. new treatments
- Problem solving – practical application of kinds of knowledge, experiments to try, "this should work" e.g. confounding symptoms
- In KW, we don't have an objective external standard – usually one-off work products
- Value in use
- KWs produce results that are necessarily incomplete and probably incorrect in one or more details
- Factual Knowledge – high quality = correct ("true", "accurate") to the appropriate level of detail
- The customer 'doesn't like it' does not count against quality
- Process knowledge – high quality = 'doability'/ease of use/regulatory compliance
- Again, 'doesn't like it' doesn't count
- Understanding knowledge – high quality = reasonability, experience, convincing, case study
- Knowledge creation – high quality = science
- Problem Solving – high quality = results (vs. cost)
- In these areas, production quality has a lower bound of comprehensibility, but improving it beyond that is probably a waste
- If our results have flaws, then our work was bad work?
- What is 'resulting' and why is it bad
- Redefine what a 'good' decision is
- The key is that the problem of resulting divorces our outcomes from the quality of our effort
- Why is resulting bad – it causes us to doubt, to change good processes for bad ones
- Avoid resulting in decision making – follow the decision process
- How to avoid resulting in Knowledge Work results – how do we know we've done good work
- Athletes and results (three point shooting)
- Knowledge work results have 1) hidden information (e.g. user needs, uncertainty about facts), and 2) risk
- So, knowledge workers have done good work when we've followed our process
- Helps avoid the perfection trap (overinvesting in quality)
- Avoiding resulting in our work
- It leads to perfectionism, which is wasteful
- Without other standards, we default to production quality, which is probably wasteful
- Avoid making our delivery processes weak (no 'change resistance' or consistency)
- Avoid resulting's sapping of our confidence
- As knowledge workers, we need to get comfortable with 'best effort'
- Develop a process to adopt changes to our processes, don't change our work processes at the drop of a hat
- Scrum/Agile project management can help, but the user has to be highly involved
- Use lots of MVPs
- Develop confidence
- Focused work for our target amount of time is 'good' work
- An experiment is good to the degree that it produces usable data
- Not to the degree that it supports a specific hypothesis
- So do good experiments
- Apply this to MVPs
Similar Episodes
Apr 30, 2025 ·36m
Apr 4, 2025 ·26m
Mar 15, 2025 ·12m
Mar 7, 2025 ·20m
Mar 6, 2025 ·20m
Mar 4, 2025 ·35m