My visibility | behaviour | trust in you
My thanks to Chris Bragg for a line of questioning that prompting these prose; Jason Hier for promoting the dialogue from which I repeat my part in here; and Dinah Turner who generated the original visual prompt. All of which started {here}, a discussion on LinkedIn. My thanks also to Bill Sherman. Another LinkedIn thread {here}, one with a challenge I accepted yesterday, and answer at the end of this blog.
Visibility of what? v | b | t in context
Visibility for my project purposes i.e., Visibility | b | t , is addressing transparency between parties. Directed towards what is known and what remains uncertain. In our projects, how much visibility are we sharing one party (project actor) to the next?
This is how visibility relates behaviour i.e., v | behaviour | t , as transparency by one party to the next. This transparency reveals or hides certain behaviour. That could be our intentions, motivations, or actions. Derived perhaps from something as simple as our hubris or belief that we are surely right. Or something more self-interested or malevolent. From these two variables we can ask if we are affording the right level of trust i.e., v | b | trust , to the exchange. Assessing all three presents an indication of collaborative nature, as it relates to all parties supporting the intended change, as project truth.
How are we safeguarding a project from what we do not know?
This sketch, from Dinah Turner, prompted the wider discussion I refer to above. If the dot was the minimal amount of necessary information, Jason Hier teased us with asking what if it was as little as 1%, then let’s respond with the question as a percentage of what? We need to have more awareness to the reality that somethings are not knowable – but that our processes need to have the adaptability to manage these later realisations.
As a graphic to reflect our limited availability of information, what was prompted here was a discussion around making best use of the little information we have. From my perspective (as related to project knowledge), the diagram also presented a third area of interest. (1) the spot of what is known; (2) the assumed everything there is; (3) a challenge to the assumption we can ever bound everything there is to know – beyond the circle. This is what Gigerenzer (2014) would reflect upon when comparing risk vs. uncertainty. It is the difference between working within a closed system vs one that interrelates to more. Or Engwall‘s “no project is an island” from which we can remove ourselves from closed system thinking in any project situation. Combining these two principles, we always have some uncertainty. I suggest the circle in the above graphic houses “the question we asked”. But outside the circle is “the question we wish we knew to pose”. From here we can hope to critically appraise the manner of any decisions being made, for what purpose, and from an information perspective we can ask “based upon what?“.
Being able to seek clarity on what the 1% represents enables better questions. Anyone who knows me, will know that my most likely answer to a question, is another question. This is because a question directs our attention to a set of assumptions and constraints. Are these parameters intended to facilitate an open dialogue, or are they intended to funnel and dissuade a wider perspective? Is this reflecting behaviour of the person posing the question, that we trust to have this right?
It is at these earliest of moments – in defining both problem and constraints – that we can begin to become unstuck. And why we should all therefore be first challenging the question, to see what visibility, behaviour, and trust, is represented. See other blogs on these areas individually, including for example sensemaking and wider problem solving perspectives.
Projects as time bound intended change
This is a dynamic position, and therefore change. In the modelling idea I have in mind, this is where my attempt to define everything by a project definition comes into play: as time bound intended change. And that any change, even one of enquiry, can be captured by this project definition.
Projects within projects
This also challenges us to consider if our collaborative practices are ever actually aimed at the same project. Or are two project actors working on their own projects and attempting to direct outcomes to their own intended outcome – even if that is at the expense of the other. I have in mind here game theory models that represent zero sum outcomes (winner:loser); or those where lesser outcomes emerge because of failures to cooperate (see prisoner’s dilemma, or tragedy of the commons, as examples).
Other factors are then able to be introduced:
- direction of influence. Interests directed into the one project, or away from the project and directed instead toward the party with most momentary influence.
- manner of project control to support the retained inward influence of both the one project aim and protection of all project actors.
These are factors that relate to potential outcomes. The one shared outcome, if we are claiming to be in the one same project. Each factor (visibility, behaviour, trust, influence, and control) the aggregation of contributing factors. So, if a question is asked with a hidden or misguided agenda in mind, the project of enquiry is immediately more likely to fail. Failure because it fails at least one participant, and probably the project overall. Or if the intent was misdirection, there was never a single project with the two parties in mind.
At bigger scale, this is why the inevitable uncertainty that exists is eroding this collaborative endeavour if it is simply defined and offloaded in contract. This is not the same as project outcome control. It is more simply a financial risk transfer with increased likelihood of dispute. Arguably a later revelation that project truth never existed. Only the roughly aligned interests of the two separate projects and outcomes each party was interested in, influencing, and operating with suboptimal visibility, behaviour, and trust.
I would argue this is the default position in construction. As one example where hidden agenda is almost always assumed, even if not shown. Low visibility as data is filtered between commercial boundaries. Malevolent behaviours. No trust. Contracts attempting to replace trust, but therein failing to regain control.
If this observation is accepted, then it offers an rough guide to likelihood of project success. If we see a project with inadequate control of its truth (the totality of visibility, behaviour, and trust) it is a riskier project than it needs to be. It is representing a project at risk of unseen influences, permitting malevolent interests, and abuses of empowerment bestowed. Therein is the prospect of increased potential for dispute, plus missed opportunity to intervene.
Are we one project? My ongoing hypothetical
I am yet to be convinced we can ever truly be one project. It is why this entire blogsite is called Projects | Within Projects. But I do think we can seek to ensure our own projects are more closely aligned. As well as all the other project assessments we undertake, I am suggesting this v | b | t assessment of the many influences, directed at the appropriateness of controls containing them, can be one of those higher level quick indications of the human made threats to success.
This affords a simple question, “why say yes to this project?“. Why as a potential project actor agree to enter this enterprise if the divergent interests are not a central focus of control? Why insure it? Why invest in it? Why be party to it? Why approve it? If one can heuristically identify this increased chance of failure, the questions you ask can all be directed this way.
This is visibility | behaviour | trust as a rule of thumb. A heuristic tool, directed at the overall collaborative interest at a project’s core. A work in progress. One that keeps me returning to first principles, new discourse, and regular revisits to this hypothesis as I go.
Agreed or not agreed – is that my question?
And finally…to the challenge I am responding to.
Can you distil your best ideas down into a simple question?
asks Bill Sherman via LinkedIn
Bill Sherman – a writer of thought leadership, and taking ideas to scale. His post yesterday was quite different. He compared NASA mission statements to those we each set ourselves. He offered contemporary examples of the questions NASA set to define their missions. Each a single question – pithy and capturing the imagination of any five year old or older still living with a sense of wonder. His challenge, which I agreed, is to set my idea into a single question. What is the essence of what this big idea is trying to do?
Bills advises us to be guided by the following:-
What’s your big idea that you’re pursuing?
How are you staying connected to your sense of wonder?
Are you able to explain that wonder to others?
Here’s a quick way to check:
1. Write your big idea in one sentence that evokes joy/wonder.
2. Then, test it out. Ask people what they think.
3. Keep going until people say “wow.”
I will confess to writing this entire blog with this question in mind. So here goes, attempt number one.
Can our modelling of projects be linked, to better guide all scales of intended change?
Version one
Can success or failure be gauged by a simple assessment of external influences and resulting appropriateness of project controls?
Version two
Projects are jeopardised if rogue influence gains control: can we avoid the invitations to fail?
Version three
[…] to be in good spirit and good health. This opening sentence is also now added to my last blog…