I push decision-making to the right people as appropriate.
To make this work, it is critical to teach decision-making. A popular method is RAPID, an acronym of 5 words that refer to the group of people involved in the steps of decision-making -Recommend, Agree, Perform, Input, Decision. This was a framework developed by Bain & Company as a systemized framework to design an action plan regarding a problem.
With the base of how a decision is made, the next step is to decide what sort of decisions exist in the organization, and how they get made. I recommend two axis:
The Scale of the Decision: What is the risk level of the decision
The Level of Process Controls: How well defined is the process around the area of the decision
Primary Investigator, Study Director, Qualified Person, Responsible Person – the pharmaceutical regulations are rife with a series of positions that are charged with achieving compliance and quality results. I tend to think of them as a giant Achilles heel created by the regulations.
The concept of an individual having all the accountability is nowhere near universal, for example, the term Quality Unit is a nice inclusive we – though I do have some quibbles on how it can end up placing the quality unit within the organization.
This is an application of the great man fallacy – the idea that one person by the brunt of education, experience, and stunning good looks can ensure product safety, efficacy and quality, and all the other aspects of patient and data integrity of trials.
That is, frankly, poppycock.
People only perform successfully when they are in a well-built system. Process drives success and leverages the right people at the right time making the right decisions with the right information. No one person can do that, and frankly thinking someone can is setting them up for failure. Which we see, a lot in the regulatory space.
Sure, the requirement exists, we need to meet it failing the agencies waking up and realizing the regulations are setting us up for failure. But we don’t need to buy into it. We build our processes to leverage the team, to democratize decisions, and to drive for reliable results.
Let’s leave the great man theory in the dustbins where it belongs.
One of the core jobs of a process owner in risk assessment is assembling this team and ensuring they have the space to do their job. They are often called the champion or sponsor for good reason.
It is important to keep in mind that membership of this team will change, gaining and losing members and bringing on people for specific subsections, depending on the scale and scope of the risk assessment.
The more complex the scope and the more involved the assessment tool, the more important it is to have a facilitator to drive the process. This allows someone to focus on the process of the risk assessment, and the reduction of subjectivity.
Always include a “do nothing” option: Not every decision or problem demands an action. Sometimes, the best way is to do nothing.
How do you know what you think you know? This should be a question everyone is comfortable asking. It allows people to check assumptions and to question claims that, while convenient, are not based on any kind of data, firsthand knowledge, or research.
Ask tough questions! Be direct and honest. Push hard to get to the core of what the options look like.
Have a dissenting option. It is critical to include unpopular but reasonable options. Make sure to include opinions or choices you personally don’t like, but for which good arguments can be made. This keeps you honest and gives anyone who see the pros/cons list a chance to convince you into making a better decision than the one you might have arrived at on your own.
Consider hybrid choices. Sometimes it’s possible to take an attribute of one choice and add it to another. Like exploratory design, there are always interesting combinations in decision making. This can explode the number of choices, which can slow things down and create more complexity than you need. Watch for the zone of indifference (options that are not perceived as making any difference or adding any value) and don’t waste time in it.
Include all relevant perspectives. Consider if this decision impacts more than just the area the problem is identified in. How does it impact other processes? Systems?
A struggle every organization has is how to think through problems in a truly innovative way. Installing new processes into an old bureaucracy will only replace one form of control with another. We need to rethink the very matter of control and what it looks like within an organization. It is not about change management, on it sown change management will just shift the patterns of the past. To truly transform we need a new way of thinking.
it’s possible to capture the benefits of bureaucracy—control, consistency, and coordination—while avoiding the penalties—inflexibility, mediocrity, and apathy.
Gary Hamel and Michele Zanini, Humanocracy, p. 15
The above quote really encapsulates the heart of this book, and why I think it is such a pivotal read for my peers. This books takes the core question of a bureaurcacy is “How do we get human beings to better serve the organization?”. The issue at the heart of humanocracy becomes: “What sort of organization elicits and merits the best that human beings can give?” Seems a simple swap, but the implications are profound.
I would hope you, like me, see the promise of many of the central tenets of Quality Management, not least Deming’s 8th point. The very real tendency of quality to devolve to pointless bureaucracy is something we should always be looking to combat.
Humanocracy’s central point is that by truly putting the employee first in our organizations we drive a human-centered organization that powers and thrives on innovation. Humanocracy is particularly relevant as organizations seek to be more resilient, agile, adaptive, innovative, customer centric etc. Leaders pursuing such goals seek to install systems like agile, devops, flexible teams etc. They will fail, because people are not processes. Resiliency, agility, efficiency, are not new programming codes for people. These goals require more than new rules or a corporate initiative. Agility, resilience, etc. are behaviors, attitudes, ways of thinking that can only work when you change the deep ‘systems and assumptions’ within an organization. This book discusses those deeper changes.
Humanocracy lays out seven tips for success in experimentation. I find they align nicely with Kotter’s 8 change accelerators.
Keep it Simple
Generate (and celebrate) short-term wins
Enlist a volunteer army
Make it Fun
Start in your own backyard
Form a change vision and strategic initiatives
Run the new parallel with the old
Enable action by removing barriers
Refine and Retest
Stay loyal to the problem
Create a Sense of Urgency around a Big Opportunity
Comparison to Kotter’s Eight Accelerators for Change
There are a few principles to make this team collaboration work.
Clear purpose: What is the reason for the collaboration? What’s the business case or business need? Without alignment on the purpose and its underlying importance to the organization, the collaboration will fail. The scope will start to change, or other priorities will take precedence.
Clear process: How will the collaboration take place? What are the steps? What is the timing? Who is responsible for what?
Clear expectations: What is the specific goal or outcome we are striving for through this collaboration?
Clear support: Problems will arise that the team cannot handle on their own. In those cases, what is the escalation process, including who and when?