<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Case Study &#8211; Leaders Protocol</title>
	<atom:link href="https://leadersprotocol.io/category/case-study/feed/" rel="self" type="application/rss+xml" />
	<link>https://leadersprotocol.io</link>
	<description>Leadership Development - Focused and Purposeful</description>
	<lastBuildDate>Thu, 22 Jun 2023 07:45:16 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://leadersprotocol.io/wp-content/uploads/2023/05/favicon-150x150.jpg</url>
	<title>Case Study &#8211; Leaders Protocol</title>
	<link>https://leadersprotocol.io</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Case Study: Priorities are like opinions &#8211; we’ve all got our own &#8230; Gaining agreement on the same ones</title>
		<link>https://leadersprotocol.io/priorities-are-like-opinions-weve-all-got-our-own-gaining-agreement-on-the-same-ones/</link>
					<comments>https://leadersprotocol.io/priorities-are-like-opinions-weve-all-got-our-own-gaining-agreement-on-the-same-ones/#respond</comments>
		
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Sun, 11 Jun 2023 19:28:16 +0000</pubDate>
				<category><![CDATA[Case Study]]></category>
		<guid isPermaLink="false">https://leadersprotocol.spectrawebdesigns.co.uk/?p=1039</guid>

					<description><![CDATA[“I thought the priorities were very clear. We have a tight timescale to deliver. What were they thinking working on that, when there’s way more important things to fix”. INTRO In the fast-paced world of fintech, clear priorities and effective collaboration are vital for success. However, a post-Series A fintech company recently engaged me as [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1039" class="elementor elementor-1039" data-elementor-post-type="post">
						<section class="elementor-section elementor-top-section elementor-element elementor-element-0465c8b elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="0465c8b" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-89c7186" data-id="89c7186" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-0a17697 elementor-widget elementor-widget-heading" data-id="0a17697" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-medium">“I thought the priorities were very clear.  We have a tight timescale to deliver.  What were they thinking working on that, when there’s way more important things to fix”.</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-f9050fc elementor-widget-divider--view-line elementor-widget elementor-widget-divider" data-id="f9050fc" data-element_type="widget" data-e-type="widget" data-widget_type="divider.default">
				<div class="elementor-widget-container">
							<div class="elementor-divider">
			<span class="elementor-divider-separator">
						</span>
		</div>
						</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				<section class="elementor-section elementor-top-section elementor-element elementor-element-f66b1e3 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="f66b1e3" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-6b037ae" data-id="6b037ae" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-4409da7 elementor-widget elementor-widget-text-editor" data-id="4409da7" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">INTRO</span></p><p><span style="font-weight: 400;">In the fast-paced world of fintech, clear priorities and effective collaboration are vital for success. However, a post-Series A fintech company recently engaged me as it faced challenges which they felt were due to an org model they had outgrown. The CEO and COO were frustrated with the team&#8217;s progress, questioning why important issues were being overlooked in favour of what they referred to as admin level work being prioritised. This case study explores their story; complexities of their roadmap, the fragmented approach of separate teams, reactive changes, pivots in focus, communication, and a hunger for clarity and alignment. By prioritising these challenges head-on, the organisation concluded the cause of the issues was not the org model and decided on a different path to develop a cohesive and high-performing team.</span></p><p><span style="font-weight: 400;">CURRENT SITUATION &#8211; PROBLEM STATEMENT</span></p><p><span style="font-weight: 400;">Within the fintech industry, complex roadmaps with numerous activities are commonplace. In this organisation, the roadmap was no exception, posing a challenge for several teams. With each team working very hard, and largely in isolation, they lacked a collective focus, their progress was hindered, and company level priorities became blurred. Additionally, frequent reactive changes from various stakeholders, including the people who’d engaged me further contributed to the lack of clarity and alignment.</span></p><p><span style="font-weight: 400;">The C-suite leaders, including the CEO and COO, grew increasingly frustrated with the situation. They believed that progress could be achieved at a faster pace and sought to address the underlying issues &#8211; the organisation was not fit for purpose.  They had a point and we agreed it certainly needed a refresh and I wondered if there were other considerations too that were maybe much closer to home. Line managers and team leaders shared similar frustrations to me, while the product teams didnt really have time to talk, and were diligently working very hard and apparently lacked the necessary alignment and cohesion to deliver optimal results.</span></p><p><span style="font-weight: 400;">UNDERSTANDING THE ROOT CAUSES</span></p><p><span style="font-weight: 400;">To identify the root causes of the challenges, a one week end-to-end review was undertaken sampling data from a range of sources in the business. Everyone recognized that effective communication was a critical factor. Information was not being effectively disseminated, leading to confusion and unnecessary delays. The absence of clear ownership and accountability for objectives further exacerbated the problem. As a result, different teams and individuals had varying interpretations of what was truly important.  Would this be fixed by a re-organisation?  There was certainly an appetite to try.</span></p><p><span style="font-weight: 400;">ALIGNING PRIORITIES AND OBJECTIVES</span></p><p><span style="font-weight: 400;">A re-org creates a massive hiatus in any business. Everything stops until everyone knows what’s happening &#8211; that is absolutely to be expected.  On that basis things were going to get a lot worse before they got better.  To mitigate this, there were also rumblings of outsourcing, something which we agreed would be the classic “Your mess for less”solution.  With some trepidation, it was agreed that before stepping into a major and potentially costly re-org, which may also have some unintended consequences, there may possibly be some quicker and easier wins to be had. That meant being clear about what we were trying to fix and what a good outcome would look like.  </span></p><p><span style="font-weight: 400;">A renewed focus on aligning priorities and objectives became imperative. The organisation embarked on a series of initiatives aimed at fostering clarity and cohesion.  Once we had a clear set of company level priorities which was easily concluded, I worked almost exclusively with the line management community working out how they’d translate them into goals that they needed to own.  That was harder!  The group needed to go on their own journey. First, these goals were theirs to define and deliver. Second, they had to do that as a collective as they were all interdependent on each other, which was an exercise we explicitly ran through to prove the point and the strength that they could gain from each other. That change journey was an iterative process, which needed time to allow individuals to develop both 121 and wider group relationships.  Simple, not always easy.</span></p><p><span style="font-weight: 400;">Clear Prioritization Framework: A comprehensive framework was developed to define and prioritize objectives based on strategic importance and urgency. This framework provided a roadmap for decision-making and resource allocation.</span></p><p><span style="font-weight: 400;">Enhanced Communication Channels: To ensure effective communication, the organisation implemented a streamlined approach to communication. Single sources of truth, owners of that truth and structured interaction started to stem the informal multiple channels of changing priority and needs based on the latest thing someone had heard.  Despite literally hating the word “Governance”, the cleanliness a simple model brought to the workplace was broadly welcomed.  Cross-functional collaborations, and transparent reporting mechanisms were introduced and shared up, down, and sideways. This facilitated the flow of information &#8211; to everyone &#8211; minimised miscommunication, and fostered a shared understanding of priorities, successes and red flags.  The news was not all good, and it didnt suddenly become a walk in the park, but everyone knew where they stood and they all got the same message.</span></p><p><span style="font-weight: 400;">Ownership and Accountability: To create a sense of ownership, objectives were clearly assigned to specific teams and individuals with interdependencies mapped. Each team member understood their responsibilities and had a clear view of how their work contributed to the overall goals of the organisation. Regular performance reviews and feedback sessions further reinforced accountability. Giving and receiving feedback was not a common cultural practice, and we worked on that to improve it.  Again, simple, not always easy &#8211; nonetheless we did see many, many more people engaging in ways they hadn’t before. </span></p><p><span style="font-weight: 400;">REFLECTING ON PROGRESS</span></p><p><span style="font-weight: 400;">As the initiatives took hold, progress became evident. The organisation witnessed improved collaboration, enhanced focus, and a shared sense of purpose. Team leaders reported higher levels of engagement and alignment among their respective teams. As an outsider looking in, I could see higher engagement between team leaders and line managers &#8211; the cross functional trip-ups were far less evident.  The CEO and COO also observed a positive shift in the organisation&#8217;s dynamics, with improved communication and a clearer understanding of strategic priorities.  They also had to up their game as they were starting to get held to account by people who in the past had been passive recipients of their requirements.  The collective understanding of the strategy, priorities and goals meant that those charged with execution had become a load more interested, engaged and concerned &#8211; no longer passive recipients, they were now playing to win. </span></p><p><span style="font-weight: 400;">CONCLUSION</span></p><p><span style="font-weight: 400;">In any business, aligning priorities and fostering cohesion is essential for success.  It’s not that people weren&#8217;t working hard, they were just working on what they felt they needed to &#8211; and that changed, often! This case study highlights two things.  First, we’re inclined to look for solutions that may well feel like we’re fixing something but aren’t.  We convince ourselves that we’re taking decisive action, and maybe sometimes deep down, we know its unlikely to be the right action.  That’s a perfectly normal human response.  We just need to check ourselves when we behave that way.  </span></p><p><span style="font-weight: 400;">Second, by recognizing the importance of effective communication, clear ownership, and a shared sense of purpose, organisations can successfully navigate the complexities of their business &#8211; and probably make it more simple in the process! Through these efforts, cultivating a high-performing and cohesive team, totally able to achieve their strategic goals becomes a reality.</span></p><p><span style="font-weight: 400;">These teams went on a transformative journey.  Relatively young, with few having more than 5-7 years experience, they worked hard to shift the only behaviours and working patterns many had ever known.  I simply provided a gentle hand on the tiller.  The team were a pleasure to work with and for the record, they still haven’t done a re-org.</span></p>								</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				</div>
		]]></content:encoded>
					
					<wfw:commentRss>https://leadersprotocol.io/priorities-are-like-opinions-weve-all-got-our-own-gaining-agreement-on-the-same-ones/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Case Study: Communicating to Succeed &#8211; Never Making Assumptions</title>
		<link>https://leadersprotocol.io/communicating-to-succeed-never-making-assumptions/</link>
					<comments>https://leadersprotocol.io/communicating-to-succeed-never-making-assumptions/#respond</comments>
		
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Sun, 11 Jun 2023 19:15:59 +0000</pubDate>
				<category><![CDATA[Case Study]]></category>
		<guid isPermaLink="false">https://leadersprotocol.spectrawebdesigns.co.uk/?p=1028</guid>

					<description><![CDATA[“Everyone knows the goals. I expect the team to work out what they need to do so we meet them, feed that back to me, and we’ll review them. I’m not doing their jobs for them”. INTRO I was approached by a business CEO who was finding difficulty maintaining alignment across her team.&#160; The strategy [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1028" class="elementor elementor-1028" data-elementor-post-type="post">
						<section class="elementor-section elementor-top-section elementor-element elementor-element-650f397 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="650f397" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-6096a9f" data-id="6096a9f" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-5d72590 elementor-widget elementor-widget-heading" data-id="5d72590" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-medium">“Everyone knows the goals.  I expect the team to work out what they need to do so we meet them, feed that back to me, and we’ll review them.  I’m not doing their jobs for them”.</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-2b34ff0 elementor-widget-divider--view-line elementor-widget elementor-widget-divider" data-id="2b34ff0" data-element_type="widget" data-e-type="widget" data-widget_type="divider.default">
				<div class="elementor-widget-container">
							<div class="elementor-divider">
			<span class="elementor-divider-separator">
						</span>
		</div>
						</div>
				</div>
				<div class="elementor-element elementor-element-2ce23d4 elementor-widget elementor-widget-text-editor" data-id="2ce23d4" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">INTRO</span></p><p><span style="font-weight: 400;">I was approached by a business CEO who was finding difficulty maintaining alignment across her team.  The strategy appeared clear,  but nonetheless without her personally applying constant attention on almost daily basis, focus was drifting and in her opinion their execution was not being progressed to either a quality or pace that would work for their strategy which had been agreed with their board. </span></p><p><span style="font-weight: 400;">CURRENT SITUATION &#8211; PROBLEM STATEMENT</span></p><p><span style="font-weight: 400;">The interdependency between a COO and the CEO (even when that role may be the same person fulfilling two functions), can inevitably create tension.   The everyday demands of the business, the COO’s “Noise”, contrasted against the CEO’s strategic requirements can sometimes seem to be a mismatch.  This is not uncommon and is perfectly understandable particularly when we consider the well used 2&#215;2 matrix that considers Important and Urgent along each axis. </span></p><p><span style="font-weight: 400;">Each person will have a different interpretation of what is urgent and important unless those criteria and the subject in hand have been clearly defined, explained, and agreed. As the saying goes, “You can do anything but you can&#8217;t do everything”, and this particularly applied here where the CEO and her wider team were indeed trying to do everything which was resulting in the business not making sustained progress, having misaligned goals sometimes conflicting with each other,  with ignorance being evident amongst the whole team.  The problem was that communication and accountability were not being explicitly agreed amongst what was a relatively small number of people. </span></p><p><span style="font-weight: 400;">UNDERSTANDABLE DIVERGENCE OF UNDERSTANDING </span></p><p><span style="font-weight: 400;">The organisation is a post-seed startup where the division of high-level accountability was very clearly defined.  The CEO was outward facing to investors,  conferences,  industry partners and regulators.  The COO was inwardly focused entirely on developing the business capability,  delivering the road map,  and building the team. </span></p><p><span style="font-weight: 400;">This portfolio arrangement worked well and had seen the business grow healthily,  establish product market fit,  secure excellent funding,  win several awards,  and secure very high profile early revenue marquee customers.  On just about any measure it is doing very well and has a great future ahead of it. </span></p><p><span style="font-weight: 400;">The CEO and COO focus however had led to a divergent understanding of what was important, what was urgent, and where the team&#8217;s focus should be with a common understanding as to why. I met with both of them individually to understand their perspectives.  The CEO had been consumed with finalising a fundraising round,  which ended up being oversubscribed (quality problem!),  securing and delivering papers at key conferences,  and working with thought leader potential clients to understand their journey and how the company would fit into it.  </span></p><p><span style="font-weight: 400;">The COO had been reassembling the team following the pandemic, establishing new working norms that would improve their outcomes,  hiring new key roles,  and accelerating the existing roadmap which was well documented and understood by everyone.   Throughout the pandemic the COO had shown great care in communicating thoroughly and frequently with the team so that they remained cohesive and did not lose the market lead they were already generating. </span></p><p><span style="font-weight: 400;">Their largely separate worlds and agreed areas of responsibility inadvertently led to a divergence of understanding,  expectation,  and reality of what each other were doing.  Their trust in each other built up over several years meant they did not see any need to be frequently peer reviewing each other&#8217;s work.  Their assumptions about their plan,  based on a scenario that was now verging on ancient history, remained their single source of truth and frame of reference.  With no ill intent, working in relative isolation, they had both sub consciously iterated and morphed their interpretation of their strategic goals,  routinely tweaked them in very minor ways to accommodate their realities in their day-to-day working life,  their priorities, and team needs based on their individual unique environment.  It was a chance meeting and conversation that led them both to simultaneously question each other about exactly what they were doing. </span></p><p><span style="font-weight: 400;">The conclusions of that conversation evidently shocked them both. They left what was an accidental discussion both feeling let down, very alone,  misunderstood,  and wondering what had gone wrong; trust had been breached.  Predictably, both wanted to critique the other&#8217;s position and both felt that they had not been privy to information and developments that were material to their personal responsibilities and portfolio.  As would be the case in any small team,  the ramifications of this conversation rippled leaving everyone feeling that the cohesiveness they believed they had was in fact a very unsteady foundation. </span></p><p><span style="font-weight: 400;">THE SOLUTION: FINDING CONVERGENCE</span></p><p><span style="font-weight: 400;">We agreed on a three step process to reestablish the cohesive momentum that had previously existed.</span></p><p><span style="font-weight: 400;">STRATEGY AND GOALS &#8211; WHAT’S THE DIFFERENCE?</span></p><p><span style="font-weight: 400;">First reflecting on Richard Rumelt, Good Strategy Bad Strategy,  we worked on re-aligning  strategy and goals.  The challenge was to make sure that we had an end to end coherent and actionable plan that focused on the most critical challenges and opportunities.   The CEO had been focused on an emerging strategy whereas the COO had been focused on very tangible immediate goals.  In fact the COO wasn’t consciously aware that the strategy was still emerging.  At some point in the past strategy and execution were aligned and cohesive,  however over time, they had become very disconnected.  This was for a number of reasons. The environment in which the CEO was working had materially changed with new investors, industry partners,  marquee sales prospects and an increasingly interested regulator.   </span></p><p><span style="font-weight: 400;">The COO had been ruthlessly focused on the road map resourcing and milestone progress having put in place effective agile practices and brought the team back together from the overly remote working style we all became familiar with during the pandemic.   Meeting the milestone KPIs,  engaging the team,  hiring new people all demonstrated tangible progress.</span></p><p><span style="font-weight: 400;">Evidently alignment had been lost.  Drawing on </span><a href="https://www.linkedin.com/in/johnpcutler?miniProfileUrn=urn%3Ali%3Afs_miniProfile%3AACoAAABkgVcByXwZ4Zke2hKjaekv4qJxDWQeqsY&amp;lipi=urn%3Ali%3Apage%3Ad_flagship3_search_srp_all%3BucsBZAAjR1K44yEy93%2FOFw%3D%3D" target="_blank" rel="noopener"><span style="font-weight: 400;">John Cutler’s</span></a><span style="font-weight: 400;"> wonderful blogs,  he maintains alignment is a dynamic equilibrium and unfortunately my client had inadvertently frozen their alignment in the past and it was becoming increasingly less relevant as each week passed.  It could be argued that the CEO and COO had achieved a form of shallow alignment where without any malice, they were ticking an alignment box, characterised by a low stakes easy to achieve check that they subconsciously felt very confident about.</span></p><p><span style="font-weight: 400;">We surfaced this and tailored our sessions to reflect the learning culture of the business.   Both the CEO and COO were very keen to genuinely understand what the hell happened!   Looking in the rearview mirror is always wholly analytical and does not serve our future in a direct way, but it is a great way to reflect and learn, and our time spent spotting the “Gotcha” moments were invaluable and led to a number of lessons being learned, heads being thrown into hands, and some laughs along the way too &#8211; all in a safe environment where vulnerability was required to maximise the benefit of the learning.   Over the course of just one day we listed a relatively small number of events that had caused the divergence over a period of almost one year.   It was not necessary for me to propose any detailed solutions as both people were very enthusiastic to apply their learnings immediately and problems were solved almost real time.</span></p><p><span style="font-weight: 400;">HOW WELL DO WE WORK TOGETHER?</span></p><p><span style="font-weight: 400;">The second thing we did was to examine the way the CEO and CEO worked together.  Whilst they&#8217;ve known each other for a significant number of years,  it seemed to me that they were using this period of time as a proxy for how well they knew each other professionally.    I turned to Hogan and proposed an assessment for both of them,  conducting individual feedback sessions and then bringing them together.  We completed this exercise and compared our findings to the lessons learned in the previous step,  which showed a strong  correlation and reinforced the value of their learning &#8211; more smiles, more insights, and a better understanding of each other for sure.  Their openness to conduct a joint session allowed us to safely and thoroughly evaluate working styles and traits that are likely to be exhibited when under pressure and examine their reputations in general.  For these two people, working closely together, this provided an elegant shortcut for them to better understand each other and avoid future trip-ups and also more importantly be able to augment each other&#8217;s strengths so that the whole is greater than the sum of its parts.   This was a highlight of the overall engagement and it was hugely rewarding to see how much value they both obtained from this process.</span></p><p><span style="font-weight: 400;">SHARING IS CARING!</span></p><p><span style="font-weight: 400;">Third, we turned to the wider team and looked at how they had impacted the situation and being impacted by it.  Drawing on Stan McChrystal, Team of Teams,  we discussed how a whole team having a complete picture of the overall mission can tangibly and positively affect the outcome.  We concluded that whilst they were very focused,  the majority, who worked with the COO had no sight of what the CEO was doing, what she was learning, and how that could affect their work.  The COO is a dedicated servant leader whose focus was the team, their well-being and of course the progress that was being made.   In short the COO/CEO relationship was a single point of failure in communication with a lack of real time information flow between them risking mission failure.  While it may not be necessary for everybody to have access to all information at all times, the risk in these circumstances of them </span><i><span style="font-weight: 400;">not</span></i><span style="font-weight: 400;"> having access to that information,  is likely to be far greater than the risk of them </span><i><span style="font-weight: 400;">having</span></i><span style="font-weight: 400;"> access to the information.  This needs a disciplined team to remain focused on their goals while scanning the wider environment for data and information that may impact their work.  We don&#8217;t want them commenting on </span><i><span style="font-weight: 400;">everything</span></i><span style="font-weight: 400;">,  but we need them to be aware of </span><i><span style="font-weight: 400;">anything</span></i><span style="font-weight: 400;"> that could hamper progress &#8211; that maybe only they will identify with. </span></p><p><span style="font-weight: 400;">The solution for this challenge was elegantly simple.  A broader sharing of information progress activities and insights would be explicitly shared as part of the weekly meeting.  Making this information share an accountable action rather than a casual update brought a focus to it that made everybody think more carefully about how they could keep each other informed at least and fully engaged at best.  Again drawing on John Cutler&#8217;s insights, alignment is always in dynamic equilibrium constantly adjusting and responding to changes. There is an overall balance but minute by minute and day by day things are shifting, adapting, bending and reconfiguring. In effect the moment you leave the meeting the system begins to recalibrate based on new information.  The team’s solution consciously recognized this hypothesis and leaned hard into it to make it work for them rather than the other way around.</span></p><p><span style="font-weight: 400;">REFLECTION</span></p><p><span style="font-weight: 400;">This engagement was not about turning strategy into action; that had already been done. It was not about focus or trying to do too much; that had already been resolved.  It was about two people’s best intent in developing their team and their business. They wanted to move as quickly as possible in an efficient manner by a division of labour where each managed a portfolio in parallel.  Their aims for efficiency unfortunately was not effective.  Effectiveness usually has a cost premium over the most efficient solution possible and sometimes that expenditure may be unnecessary. The challenge is that it is very hard for us to predict when that may be the case and where it is not, so finding an optimal efficient-effective path, AKA adaptability, seems to be a panacea we are all seeking.</span></p><p><span style="font-weight: 400;">By not attending to our needs as individuals to work together to the best of our ability, respecting that we may not know each other as well as we might like to think we do, forging forward can create speed yet not velocity.  An item oscillating about a fixed point has high speed but gets nowhere, just generates heat.  A projectile, on the other hand, moves from A to B at high velocity also creating heat.   It seems to me that very often in business speed and velocity are words that we may interchange without consciously understanding the implication. In this case, although inadvertently, speed was trumping velocity and unfortunately we didn&#8217;t know that was happening.  A chance meeting lifted a stone and lots of things wriggled out.  This trigger created an emotional response between two people causing a hiatus that was sufficient to potentially stall the company because trust had been breached;  expectations would not be met or at least be very flawed, time would be wasted, valuable resources used unwisely, and credibility damaged. Two very talented people were now increasingly locked in a cognitive emotive loop, knowing that they needed to find an “out”. Recovery had to be quick, reliable, with complete buy-in across the organisation. Failure to do so would risk customer dissatisfaction, raising investor concern, and hard won brand rep would be damaged.  </span></p><p><span style="font-weight: 400;">Rapid intervention, a sense of urgency, and an acceptance of a challenge knowing that it can be resolved were the key success factors in this engagement which lasted just over one week. Solutions do not need to be complicated or expensive to implement.  Blending the subject matter expertise and contextual knowledge of the CEO and COO,  alongside a broader experience base, and drawing on best practice academic and contemporary literature provided both an effective and efficient resolution and reinstated the solid foundations on which this successful business will undoubtedly continue to grow. </span></p><p><br /><br /></p>								</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				</div>
		]]></content:encoded>
					
					<wfw:commentRss>https://leadersprotocol.io/communicating-to-succeed-never-making-assumptions/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Case Study: Leadership alignment &#8211; achieving dynamic equilibrium?</title>
		<link>https://leadersprotocol.io/leadership-alignment-achieving-dynamic-equilibrium/</link>
					<comments>https://leadersprotocol.io/leadership-alignment-achieving-dynamic-equilibrium/#respond</comments>
		
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Sun, 11 Jun 2023 19:06:09 +0000</pubDate>
				<category><![CDATA[Case Study]]></category>
		<guid isPermaLink="false">https://leadersprotocol.spectrawebdesigns.co.uk/?p=1023</guid>

					<description><![CDATA[“I&#8217;m busy as hell, busting my ass every day, evening, and most weekends, and then I get a call from my boss who says we need an urgent meeting as I&#8217;m not adding the value as a leader that’s expected” INTRO I was engaged by a tech services business where the two co-founders had hired [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1023" class="elementor elementor-1023" data-elementor-post-type="post">
						<section class="elementor-section elementor-top-section elementor-element elementor-element-e85fd49 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="e85fd49" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-1efab96" data-id="1efab96" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-95b8b03 elementor-widget elementor-widget-heading" data-id="95b8b03" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-medium">

“I'm busy as hell, busting my ass every day, evening, and most weekends, and then I get a call from my boss who says we need an urgent meeting as I'm not adding the value as a leader that’s expected” 
</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-9c9af3a elementor-widget-divider--view-line elementor-widget elementor-widget-divider" data-id="9c9af3a" data-element_type="widget" data-e-type="widget" data-widget_type="divider.default">
				<div class="elementor-widget-container">
							<div class="elementor-divider">
			<span class="elementor-divider-separator">
						</span>
		</div>
						</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				<section class="elementor-section elementor-top-section elementor-element elementor-element-8e54828 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="8e54828" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-ed0b7c6" data-id="ed0b7c6" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-5cd1fc2 elementor-widget elementor-widget-text-editor" data-id="5cd1fc2" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">INTRO</span></p><p><span style="font-weight: 400;">I was engaged by a tech services business where the two co-founders had hired a third senior leader as the organisation had grown from 4 to 40 in just over a year.  Their hire was a great generalist who could turn her hand to the vast majority of tasks, both strategic and operational, that needed to be fulfilled to keep the business growing and evolving as it did.  An utterly safe pair of hands, she came with an impeccable track record and her commitment was assured.  </span></p><p><span style="font-weight: 400;">Despite settling in quickly and efficiently getting to grips with her portfolio, embracing the empowerment offered by the two co-founders, both of whom now had time to focus on product development and fundraising.  With a runway of some 18mths, they had milestones to address which they concluded were theirs and theirs alone to resolve.  </span></p><p><span style="font-weight: 400;">CURRENT SITUATION &#8211; PROBLEM STATEMENT</span></p><p><span style="font-weight: 400;">The epicentre of many organisations’ pressure points is often the intersection of the demands placed on us to ensure day to day business takes place alongside making sure we make the strategic gains that have been carefully planned and agreed.  This is hard and anyone suggesting otherwise maybe hasn’t actually been there.  It is too easy to be “busy as hell” and yet not be making the progress that is expected or needed.  </span></p><p><span style="font-weight: 400;">The problem was that the teamwork between leaders was dysfunctional, leading to ineffective execution, and despite everyone’s best intent had led to a situation characterised by frustration and doubt which was now threatening the wider organisation and its positive trajectory. The ramifications of a communication breakdown need no discussion here; we’ve all seen it, whether in our personal or professional lives.  </span></p><p><span style="font-weight: 400;">ACCEPTANCE THAT THERE ARE TWO SIDES TO THE STORY </span></p><p><span style="font-weight: 400;">At the point in time I was engaged in this business, there had already been some deterioration in teamwork between the leadership, communication, masked breakdowns in relationships with brave faces being put on when needed, and with an underlying tenacity of “We’re not going to let this damage us”, which whilst laudable, bordered on being stubborn to a situation that wasn’t going to improve based on more of the same effort being expended, no matter how positive the intent.  The fact that someone was helping them, i.e., me, was all I needed to be fairly sure that this was a problem that certainly could be resolved.</span></p><p><span style="font-weight: 400;">There was no doubt that the attractiveness of the product, a buoyant market, the business was well funded and hiring plenty of needed people.  The GTM had worked well, with some high profile customers on boarded, and an appetite from the founders to go bigger, faster! This led to accelerated hiring, an aggressive earned PR campaign, various conference speaking slots, and most importantly, a plethora of ideas, needs, and suggestions from the high calibre talent joining at a almost a fortnightly rate.   This is a predictable situation for a successful start up, where chaos becomes the norm as the organisation battles into adolescence.  This “success” was where I pointed to, drawing on personal experience, as a potential source of the frustrations being felt by only a few, but that were also likely to quickly spread throughout the business unless the contagion was addressed &#8211; chaos and structure need to co-habit; empowerment and process governance can be helpful; “fluid direction” trumps everyone focused on their thing.  The amount of activity was becoming impossible to manage, remain focused, and yield the desired results.  To be fair, this was to an extent always going to be the case, which is perfectly fine, but how it was dealt with could be a make or break factor for the leadership team. </span></p><p><span style="font-weight: 400;">WORKING TOGETHER AS A TEAM</span></p><p><span style="font-weight: 400;">No matter how insurmountable the task list, the demands of the roadmap, the customer expectations, and the periodic crises many of us will have faced, there are some things we can predict or adapt to, understand, and optimise that are wholly within our control. </span></p><p><span style="font-weight: 400;">The first one that springs to mind for me is how we work together. The choices we consciously and subconsciously make about the way we interact with each other.  It sounds so obvious, and yet in my experience all too often we don’t spend enough time understanding each other so we can at least try with some success to get the best out of everyone when the going gets tough.  That applied here.  The leadership team were rarely in the same place for any length of time.  The three of them had markedly different historical relationships; they had built their relationships based on different contexts, during different times, with different priorities.  All quite understandable and pretty much impossible to avoid.  What they hadn’t done was calibrate, align, and actually become a team.</span></p><p><span style="font-weight: 400;">Peer leader relationships and relationships with bosses tend to be the most important ones to watch and the ones that can have the most impact &#8211; both positive and negative. In my opinion, a very good way of understanding this is by reading </span><a href="https://www.wiley.com/en-us/The+Five+Dysfunctions+of+a+Team%3A+A+Leadership+Fable%2C+20th+Anniversary+Edition-p-9780470893869" target="_blank" rel="noopener"><span style="font-weight: 400;">Lencioni</span></a><span style="font-weight: 400;"> and The Five Dysfunctions of a Team.  Told as a story, I pretty much defy anyone not to at some point nod in agreement as a point made in it totally resonated.  So, in  the interests of TLDR, what does Five Functions tell us?</span></p><p><span style="font-weight: 400;">I think most fundamentally its message to me was that much of our communication as leadership teams is transactional at best and toxic at worst, though I’d stress not intentionally so.  The symptoms that Lencioni describes all seem to come about because we don’t invest in working with each other in a quality, authentic way.  If you’re not familiar with the Five Dysfunctions here they are:</span></p><ul><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Absence of Trust</span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Fear of Conflict </span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Lack of Commitment </span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Avoidance of Accountability</span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Inattention to Results </span></li></ul><p><span style="font-weight: 400;">Note &#8211; all of these are subjects in their own right.  I talk about them on my blog page. </span></p><p><span style="font-weight: 400;">In my initial discussion with the leader whose quote is at the head of this blog, all five dysfunctions came to mind.  It seemed to me that her boss didn&#8217;t trust her.  That lack of trust hadn’t come about overnight and after our conversation it was clear that opportunities for discussion had occurred several times in the preceding months and both had in some way avoided them for whatever reason we’d yet to uncover. </span></p><p><span style="font-weight: 400;">The commitment to targets and goals was at best ambiguous leading to an inadvertent lack of commitment with no malice intended.  Lots of targets existed, awareness of them was pretty good, and at the same time the collective pledge to them seemed absent.</span></p><p><span style="font-weight: 400;">The ambiguity of commitment so often leads to accountability being a problem and inevitably without clarity the results were not playing out the way the CEO wanted.  It’s a safe bet to assume that none of this was intentional &#8211; no one wants these challenges when trying to develop, grow, and even just run a business, but they happen often in many organisations to many of us. </span></p><p><span style="font-weight: 400;">As such, each member of the leadership team was looking at the results that mattered most to them as individuals, not as a team, and it&#8217;s no surprise that there was collective inattention to the most important results, which led to frustration. </span></p><p><span style="font-weight: 400;">We agreed that leveraging Lencioni’s work and applying it where the fit worked would be a practical and efficient approach, seeing what else, if anything we encountered along the way. It was also apparent that the way in which each of the leadership team saw the world and interpreted it was very different; their approaches, needs, expectations all had noticeably contrasting profiles.  To provide a foundation and catalyst to engage in a structured discussion about their strategy execution, and because the team very much wanted to repair this situation, explicitly understanding each other better was a fundamental foundation stone we had to lay.  </span></p><p><span style="font-weight: 400;">USING OUR STRENGTHS &#8211; KNOWING EACH OTHER </span></p><p><span style="font-weight: 400;">Taking the time to better understand our peer group at an individual level and team level can be really useful.  There’s many tools that can help with profiling and the best one I’ve found is </span><a href="https://www.hoganassessments.com/" target="_blank" rel="noopener"><span style="font-weight: 400;">Hogan</span></a><span style="font-weight: 400;">.  The reason I like to use it with businesses I work with is because it examines the person’s reputation as well as their own identity.  In any team setting, our reputation &#8211; that which exists in the outside world and created by others as well as ourselves is often more important than identity, that which we see of ourselves when we talk about getting stuff done.</span></p><p><span style="font-weight: 400;">Let&#8217;s take the example in this blog.  Both parties in the situation have created reputations over time with various episodes where they have come together.  There’ll be good, bad and a million moments in between that have built a complex, subjective, and as research shows, a consistent profile.   What we also know is that our ability to “see” our own reputation is not great and so we carry on doing things that aren’t helpful, often because there’s a lack of trust and a fear of conflict.  Teams who want to address their trust and conflict performance often find tools like Hogan a useful catalyst to break the ice so to speak and explicitly set out to learn more about one another, and especially what we may well experience when colleagues or ourselves are faced with stress and pressure.  </span></p><p><span style="font-weight: 400;">If there’s an authentic intent to work together, the vulnerability of having your reputation profile shared can be a powerful tool to both help people learn about one another and also quite probably avoid pitfalls like the ones we see in this example.  It strengthens teams and  provides organisations with a differentiator that is very hard to copy, makes them more attractive to work at, and increases their performance. And, yes. this takes commitment and some quality time, but the results give back over and over again.    </span></p><p><span style="font-weight: 400;">RENEWED UNDERSTANDING </span></p><p><span style="font-weight: 400;">The Hogan process can create a safe environment from which teams can progress fast and cover ground easily that previously had been either implicit or explicit “no go” territory.  What first came out of this particular process was that the founders and their new leadership team colleague had entirely different views of their relationship. The new team member saw herself as someone to tend to that which the founders didn&#8217;t want to do, be a safe pair of hands, make sure that the growth profile was properly managed, and that details were attended to promptly and efficiently.  This in turn would enable the founders to focus on their strategic client goals and their investor community.  The founders on the other hand saw her as a partner, a third brain at the table to enhance and enrich the debate, contribute to the direction, and own the delivery and execution of the co-created strategy. </span></p><p><span style="font-weight: 400;">So first the good news &#8211; some really useful overlap in understanding that provides a platform on which to work.  The not so good news was that the understanding of what was a priority was largely missing.  </span></p><p><span style="font-weight: 400;">An example was IT.  In a team of 4, it&#8217;s pretty easy, by the time you get to 40, hardware, software, security, licences … and so the list goes on, have now become an enterprise “thing” that someone needs to deal with.  The organisation had learned a behaviour that our new leader would take care of these things, and she did, very well.  The problem was that it was now taking time that was not budgeted for, that she couldn&#8217;t just stop doing it, and that the founders wondered why the hell was </span><span style="font-weight: 400;">she</span><span style="font-weight: 400;"> the one ordering laptops and buying software licences. To her, if she didn’t do it, who could she pass it off to?  She had been forced into learning the ins and outs of their suite and to not do it would hamper people’s work, which would look bad on her, and so it would just be best to just keep doing it … after all it&#8217;s only “one thing”.</span></p><p><span style="font-weight: 400;">So whilst the very necessary IT ordering process was working just fine &#8211; with all the important benefits that brought, the founders were left expecting great things to start happening, for meetings to be arranged to refine and enhance the growth plans, only to be met with relative silence, because she didn’t want to be bothering them with more trivial matters and was focused on her goals that once in train would be revealed to the founders … once she had all the other things which needed fixing, fixed!</span></p><p><span style="font-weight: 400;">Assumptions had been made about priorities and the way delivery execution would happen by both the founders and their new colleague.  The collective understanding, alignment, and agreement about their goals and targets was largely missing until a more in depth discussion had taken place.  </span></p><p><span style="font-weight: 400;">THE SOLUTION </span></p><p><span style="font-weight: 400;">The renewed understanding which helped each of them appreciate the reputations they held with each other (and across their wider teams), informed how best they could look to the future with a more robust, transparent, and resilient way of working.  </span></p><p><span style="font-weight: 400;">Re-sharing the business strategy to ensure their interpretation of it was aligned, that their execution plan was optimised, and recognising that delivery means many things for the whole to work together was a major step. As well as understanding the strategy, sharing openly their perceived implications for the delivery was a cathartic exercise.  For example, the volume of clients, coupled with the product development ideas, alongside the hiring plan looked exciting and everything they could wish for, and at the same time caused concern that things just didn&#8217;t add up to either being feasible.  </span></p><p><span style="font-weight: 400;">This led to a prioritisation exercise where the goals, objectives to reach them, and the metrics that would measure success were debated in depth, encouraging conflict to take place so that differing perspectives could authentically be exposed and understood.  The increased trust between them helped “push back” to happen, rather than tacit acceptance.  The challenge that remained was the day to day “Noise” that could not be ignored because it was a necessary overhead to run the business, but nonetheless, even when done perfectly, would not provide the growth that was the target.  Recognising how the “Noise” and the strategic priorities could cohabit with key improvement targets in place, whilst committing to very defined priority strategic goals took time and put the team through its paces.  Such circumstances are never perfect and compromise is essential as is the reality of what is needed and how it can be achieved. The road was still bumpy for sure, but at the same time the progress in the interactions was noticeable.  </span></p><p><span style="font-weight: 400;">A recurring problem that had led to the frustrations were the lack of a common means of measuring progress.  With the changes agreed to the priorities and delivery plans, having  a scoreboard that had the same meaning for the team was important.  The measures and targets would also be shared with the wider team and so the focus moved to solving this.  We workshopped a process to be clear on company level metrics for the revised goals and objectives, designed a scoreboard that made sense, was intuitive and could easily be shared.  Finally, we returned to the relationships in the team and worked through how the metrics and scoreboard would be used to ensure accountability.  This last part, always the hardest, demands that each person in the team puts the team before themselves, and that everyone is willing to call each other out where things don’t happen that were promised.  By supporting and challenging in equal measure, the team got there with a system in place that was uniquely tailored to suit them. </span></p><p><span style="font-weight: 400;">LOOKING FORWARD </span></p><p><span style="font-weight: 400;">An aligned leadership team provides the footings on which to build a cohesive delivery plan for the rest of the team.  In this case they role modelled their expectations and took a very hands-on approach to sharing the fruits of their work across the organisation.  Stand alone, this brought an improvement in clarity and focus.  Each team was then expected to work together to draft a delivery plan for themselves drawing on the company level goals.  They worked with the leadership team to develop their practice of improving their collective understanding of the business strategy, defining their targets and metrics based on clear priorities, and working through their models of accountability could all be done using the process the leadership team had developed with me.  Simple, but not easy.  </span></p><p><span style="font-weight: 400;">For example, this process took time, and whilst a valuable investment for the business, a demand that took away from the “Noise’ that had to be tended to every day.  The leadership team consciously recognised this and at the same time impressed upon everyone that this process was one they had been through and was vital that everyone else did, with the same commitment, so that they could all continue to build the business as they intended. The collective common purpose was accepted by almost everyone and amplified the pace and quality of progress.  Each team built its own measures, shared them with their peers and the leadership team.  By the end of the process, all 40+ people were clear, if not wholly in agreement, and committed to the roadmap and its measures of success.  Largely facilitated by the person who was the original subject of frustration, this case study is testament to her and her leadership team colleagues’ want to address challenges they knew they faced. </span></p><p><br /><br /></p>								</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				</div>
		]]></content:encoded>
					
					<wfw:commentRss>https://leadersprotocol.io/leadership-alignment-achieving-dynamic-equilibrium/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Leader’s Protocol Methodology: Phase 1 Case Study &#8211; Purpose and Progress</title>
		<link>https://leadersprotocol.io/leaders-protocol-methodology-phase-1-case-study/</link>
					<comments>https://leadersprotocol.io/leaders-protocol-methodology-phase-1-case-study/#respond</comments>
		
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Sun, 11 Jun 2023 20:04:46 +0000</pubDate>
				<category><![CDATA[Case Study]]></category>
		<guid isPermaLink="false">https://leadersprotocol.spectrawebdesigns.co.uk/?p=1044</guid>

					<description><![CDATA[I was engaged by a B2B Consulting services and software business.  The objective was to establish what was preventing them from performing as they had previously been and to formulate a plan to ensure the coming year’s targets were achieved.  There were inclines and murmurs about focus, organisational change, things not being as they once [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1044" class="elementor elementor-1044" data-elementor-post-type="post">
						<section class="elementor-section elementor-top-section elementor-element elementor-element-62b81b5 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="62b81b5" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-8aa27ed" data-id="8aa27ed" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-4fc46cb elementor-widget elementor-widget-heading" data-id="4fc46cb" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-medium">I was engaged by a B2B Consulting services and software business.  The objective was to establish what was preventing them from performing as they had previously been and to formulate a plan to ensure the coming year’s targets were achieved.  There were inclines and murmurs about focus, organisational change, things not being as they once were, and the need for more governance and process, but nothing had been discussed, agreed or disagreed and concluded.</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-a5fda03 elementor-widget-divider--view-line elementor-widget elementor-widget-divider" data-id="a5fda03" data-element_type="widget" data-e-type="widget" data-widget_type="divider.default">
				<div class="elementor-widget-container">
							<div class="elementor-divider">
			<span class="elementor-divider-separator">
						</span>
		</div>
						</div>
				</div>
				<div class="elementor-element elementor-element-9cbd4a8 elementor-widget elementor-widget-text-editor" data-id="9cbd4a8" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">COMPANY INFO</span></p><p><span style="font-weight: 400;">At just over 8 years old it had grown successfully and been well funded and continued to be positively supported by its investors.  Made up of a highly talented team of around 170 people ranging from early career to very mature and most educated to degree level or above they boasted a diverse successful pool of talent.   They adopted a hybrid model of working with some people office based and some remote spanning two continents.  Just under 33% the employees had joined the business in the last 18 months.</span></p><p><span style="font-weight: 400;">Financially the business had recently become profitable and was generating free cash flow.   investment was still needed to enhance the product and develop new streams of revenue that had been identified through customer insight.</span></p><p><span style="font-weight: 400;">CURRENT SITUATION &#8211; PROBLEM STATEMENT</span></p><p><span style="font-weight: 400;">When I was engaged in the business the initial growth they had worked hard to generate was starting to falter.  The strategy had evolved and pivoted from its original stable position that was well known by the majority of the longer serving employees.   The market was strong, their customers were very satisfied,  their industry profile was very positive,  and their resources plentiful to ensure they were able to service their existing base and sales pipeline.   </span></p><p><i><span style="font-weight: 400;">The problem was clear &#8211; Why should growth be slowing at this time?</span></i><span style="font-weight: 400;"> </span></p><p><span style="font-weight: 400;">Despite the changes to the strategy the well-established leadership team were confident that it was clear,  made sense,  and certainly within their ability to deliver it.  They had developed several tried and trusted methods over several years that had brought seed and marquee customers, user growth, and initial revenue streams, all of which offered important proof points on which to build.  As a smaller business, the majority of people had been exposed to decisions, debate, and general exploration around the strategy, even though in those earlier days, it was apparent that rather than being a strategy, it was more a list of “stuff to be done”.</span> <span style="font-weight: 400;">The board was very supportive of the leadership team and expressed confidence also in the direction, targets,  and overall rationale.  </span></p><p><span style="font-weight: 400;">DYSFUNCTION &#8211; ALIGNMENT IN THE EXEC TEAM AND LEARNED BEHAVIOURS</span></p><p><span style="font-weight: 400;">Phase One was to take stock of the situation in and with the leadership team.   Most importantly to understand how the leadership team were representing themselves to each other and also equally importantly to the teams they led who would be executing the strategy.  Whatever they are being and doing would inevitably be reflected into the broader organisation and their approach mirrored. Teams working for each of the execs were demonstrating learned behaviours from them &#8211; sometimes very consciously, sometimes not, and for better or worse, recognising that there was absolutely no malice or bad intent.  We used the Hogan assessment as a tool to help the leadership team understand better their reputations between themselves as a team, and also what their functional teams most likely believed about them.  Hogan is a proven assessment tool that predicts reputation.  This was important because as well as understanding themselves better, understanding how others’ perceived the leadership team, both amongst the peer group and out into their functional teams was valuable in understanding the organisational dynamics.  Hogan also offers a prediction of how we may behave when under pressure or stress.  It’s been shown that our strengths may well become derailers; they become over indexed and the talents that brought success previously may well now be things that get in our way and prevent further progress.  Having been used by over 2 million professionals and with 30 years of research behind it, Hogan is a highly reliable, valid, and practically useful tool that has helped many organisations identify pathways to problems often hiding in plain sight.</span></p><p><span style="font-weight: 400;">DIAGNOSTIC &#8211; EXEC TEAM EXPLORATION </span></p><p><span style="font-weight: 400;">The hypothesis that the leadership team were in some way responsible for the faltering growth was tabled, explored, and accepted. This was an important first step in understanding what leadership behaviours, influences,  and dynamics may have contributed to the situation.  Conducting one to one meetings and a team debrief we were able to paint a landscape of the team&#8217;s strengths and derailers at both an individual level and as a group, tightly contextualised to their situation and objectives.  The willingness of the leadership team to share their data provided the opportunity to both enhance trust between them and in doing so reveal vulnerability that otherwise would have remained at least unspoken and quite possibly hidden.   When authentic discussions take place in a team setting, we learn things about each other that help us fill in gaps that previously we had made assumptions about, often wrong, sometimes plain ignorant.  In short, as trust grows, so do the conditions to improve performance.</span></p><p><span style="font-weight: 400;">SOLUTION TO THE INITIAL PROBLEMS</span></p><p><span style="font-weight: 400;">The Hogan process helped create a conducive environment and provided the catalyst and lever for us to explore with the leadership team their aspirations for their business,  better understand how their working style had contributed to successes to date, explore more freely the problems they felt existed,  and what they would change to revitalise their success trajectory.  </span></p><p><span style="font-weight: 400;">We ran a single whole team Workshop session to deep dive into what the business was trying to cause as its very purpose for existing.  We closely looked at the business’s short but valuable history to understand the way they had evolved as a team as much as how the business had, carefully probing how the two were linked, or not &#8211; whether for good or bad.  The culmination of Phase 1 were the conclusions the team reached themselves as to:</span></p><ul><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">What they would change to take the business forward?</span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">What did that imply for themselves and their teams?</span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">What would the change demand from them and more importantly their teams if it were to be successful? </span></li></ul><p><span style="font-weight: 400;">BENEFITS</span></p><p><span style="font-weight: 400;">This exercise illustrates a number of things and provides tangible proof points and value to the team that stand alone as practical usable outcomes that can be immediately put to positive and constructive use.  </span></p><ol><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It offers an objective, safe, constructive facilitated self-assessment of the organisation’s health defined by observing the amount of politics, levels of confusion, morale, and productivity. </span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It signposts the level of leadership alignment and commitment to The Team,  their levels of resilience,  and common understanding of the business&#8217;s position and priorities right now.  </span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It provides an indication of the leadership team&#8217;s readiness to embark any change they may wish to implement</span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">It provides an initial indication as to what it would take from their teams to make their strategy a reality.   </span></li></ol><p><span style="font-weight: 400;">Standalone this phase of the engagement has tangible value for the leadership team because they better understand each other on their collective ability to address the challenges they face.  The engagement, structured to be flexible and adaptable could have ceased at this point with tangible value, benefits, and progress made for the leadership team to pursue themselves.  </span></p><p><span style="font-weight: 400;">Leaders often know what needs to be done, and establishing a setting where that can be distilled effectively and efficiently provides sufficient leverage for the magic to happen when any group of passionate, aligned, and positive people come together.  Recognising that as a single group alone, little will happen is the next step to take and one that maybe sees a dilution of effort and commitment beyond the confines of the executive team.  </span></p><p><span style="font-weight: 400;">OUTCOME </span></p><p><span style="font-weight: 400;">The leadership team had identified what they felt needed to change and why, an agreed way forward, and their role as a collective First Team in leading and enabling its success. The foundation stones for the next chapter were laid. </span></p>								</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				</div>
		]]></content:encoded>
					
					<wfw:commentRss>https://leadersprotocol.io/leaders-protocol-methodology-phase-1-case-study/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Leader’s Protocol Methodology: Phase 2 Case Study &#8211; Blueprint for Execution</title>
		<link>https://leadersprotocol.io/leaders-protocol-methodology-phase-2-case-study/</link>
					<comments>https://leadersprotocol.io/leaders-protocol-methodology-phase-2-case-study/#respond</comments>
		
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Sun, 11 Jun 2023 20:07:39 +0000</pubDate>
				<category><![CDATA[Case Study]]></category>
		<guid isPermaLink="false">https://leadersprotocol.spectrawebdesigns.co.uk/?p=1049</guid>

					<description><![CDATA[When the execution action begins, the focus has to centre on those leaders who will do the heavy lifting and grind out the progress. Engagement with these tiers of leadership cannot be underestimated in ensuring that intent does indeed become reality. Phase 2 of our engagement revolves entirely around the line management community.  Defining that [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1049" class="elementor elementor-1049" data-elementor-post-type="post">
						<section class="elementor-section elementor-top-section elementor-element elementor-element-89f5a90 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="89f5a90" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-c08ad3c" data-id="c08ad3c" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-4f3ef2e elementor-widget elementor-widget-heading" data-id="4f3ef2e" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-medium">When the execution action begins, the focus has to centre on those leaders who will do the heavy lifting and grind out the progress.  Engagement with these tiers of leadership cannot be underestimated in ensuring that intent does indeed become reality.</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-ad0ea7f elementor-widget-divider--view-line elementor-widget elementor-widget-divider" data-id="ad0ea7f" data-element_type="widget" data-e-type="widget" data-widget_type="divider.default">
				<div class="elementor-widget-container">
							<div class="elementor-divider">
			<span class="elementor-divider-separator">
						</span>
		</div>
						</div>
				</div>
				<div class="elementor-element elementor-element-85079fc elementor-widget elementor-widget-text-editor" data-id="85079fc" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">Phase 2 of our engagement revolves entirely around the line management community.  Defining that community is quite easy.  It&#8217;s those people who are not considered the leadership team of the business but do have leadership responsibility.  This tier of the business is arguably the most important in translating strategy into execution.  This is because they are the people who will really get their hands dirty in ensuring that tangible progress is being made on a day-to-day basis.  Given the right strategic direction, this group of people are the critical success factor in engaging their teams and most importantly cohesively working together as a peer team themselves.  It may be that there are more than one layers of  leadership that may be addressed in different ways or combined as a larger quasi-peer group, comprising various line management sub groups that can usually easily be grouped to provide support for one another.  </span></p><p><span style="font-weight: 400;">THE ROLE OF THE LINE MANAGER </span></p><p><span style="font-weight: 400;">Sometimes sandwiched between the leadership team and the broader employee population,  the line manager could be said to have the hardest job in the business juggling the needs of the team she leads and ensuring that the broader corporate Direction is being followed.  In the case of strategy execution it&#8217;s vital that their understanding of what is required is contextualised and shared in a way that is A two-way communication process that goes far beyond the classic Cascade. </span></p><p><span style="font-weight: 400;">The leadership team will expect line managers to perform and Lead their teams hugely contributing to the success of the business.  It&#8217;s vital therefore that their role is respected and  that they&#8217;ll listen to as well as communicated with.  This approach will undoubtedly improve their engagement,  likely improve the environment for them to work together as a peer team,  and enable them to demonstrate to their teams that their views are valid and they are respected as an important component of the business success.  </span></p><p><span style="font-weight: 400;">REPEATING PHASE 1 WITH THEM &#8211; INFORMED BY THE LEADERSHIP TEAM PROCESS </span></p><p><span style="font-weight: 400;">The outputs from the leadership team process were presented to the line management community by the leadership team.  This offers an authentic way for the C-suite to share their experience, demonstrate and role model vulnerability,  explain their learning,  and generally positively develop their relationship and levels of trust with their wider team, sharing information that is both vitally important for success and most likely will increase the level of Engagement from their teams. Especially important was to discuss what the organisation was trying to cause.  This choice of language usually helps people frame their professional life in a slightly different way.  We often talk about what we do at work or what successes and failures we&#8217;ve had at work.  We probably infrequently talk about or frame conversations about what we&#8217;re trying to cause at work.  Almost every organisation is trying to cause something and understanding the very essence of what that is provides a richer context for the rest of the team’s work through this process to take place.   The notion of cause can also be applied at the personal level.  Asking people to consider what they personally are trying to cause helps join together their collective reason for being alongside their more personal and maybe private rational desires and practical reasons for the work they do. Asking them to share their thoughts can be a powerful exercise to help build trust through collective demonstrations of vulnerability,  helping us understand our colleagues far better than we have previously, which in turn has been shown in many situations to create higher performing teams against almost any criteria you would wish to measure. </span></p><p><span style="font-weight: 400;">At this stage constructive dialogue is encouraged and facilitated in order to provoke some constructive conflict create real conversation about the real issues and most importantly set the line management team up for their journey, equipped with the raw materials as to how they will become the conduit that will translate strategy into execution and then go on to deliver it.</span></p><p><span style="font-weight: 400;">UNDERSTANDING THE STRATEGY, AND WHY ITS RELEVANT FOR ME </span></p><p><span style="font-weight: 400;">It&#8217;s important before getting into the details to create the environment for this group for them to believe and understand that they are a team.  We used the Myers-Briggs tool to help them understand their behavioural preferences and how they could work optimally as a team drawing on each other&#8217;s strengths and recognizing ways of working that may be quite alien to what they practise as individuals on a day-to-day basis.  Predictably this exercise is good fun, helps people to get to know each other better, and often allows conversations to take place which otherwise May well not have done.  The outcome from this exercise helps the group become a team by increasing their trust in one another,  expressing commitment to the process, and welcoming constructive conflict as a useful tool for them to collectively develop. </span></p><p><span style="font-weight: 400;">HOW DO I CONTRIBUTE AS A LEADER IN THE BUSINESS &#8211; WHAT ARE MY TEAM’S GOALS</span></p><p><span style="font-weight: 400;">The foundation stone of this part of the process was for the group to fully appreciate and embrace that they are a team and that this is their first team.  They will each have a functional team beneath them for which they are accountable to lead,  however the team that is most important for their collective success comprises the people in the room with them at that moment.  </span></p><p><span style="font-weight: 400;">Continuing from the discussion with the leadership team about the strategy,  time was now spent getting the group to synthesise their learnings and contextualise what they had heard from the leadership team into language processes and artefacts that were most relevant for them and those they lead.  This prerequisite of really understanding the strategy was vital as a prelude to them considering their goals for the coming year.</span></p><p><span style="font-weight: 400;">Most company targets are lagging indicators meaning that success or otherwise will only be known after the event.  For example a percentage increase in profitability can only be measured after the period has expired.  Such measures are very unhelpful for operational managers and leaders to use as a basis for targets because they cannot measure their progress effectively and often they do not own the target.  </span></p><p><span style="font-weight: 400;">We needed to change the thinking of the group to consider leading indicators that could be used to predict the performance of the lagging indicator.  For example, if the group knew customers were particularly satisfied if they experienced XYZ,  then focusing on XYZ as their measure could be a reliable predictor of customer retention improving at the end of the period,  which is a lag indicator.   This approach needs the line manager team to both have confidence in themselves as subject matter experts, knowing their business, and the ability to translate lagging indicators into leading indicators. </span></p><p><span style="font-weight: 400;">Demonstrable empathy and respect is essential at this stage of the goal setting process.  The noise in any organisation that line managers deal with on a day-to-day basis cannot be underestimated.  It&#8217;s likely that even with world class efficiency and automation programs that the majority of the noise will not go away or will be replaced by new noise.  This cannot be understated and helping line managers compartmentalise the time they need to focus on the strategic goals recognizing that they need to keep routine BAU activities underway at the same time is important to maintain and develop empathy and trust and recognize their challenges whilst at the same time being explicitly clear about the need for focus and relentless execution on the strategic goals.  </span></p><p><span style="font-weight: 400;">Prioritisation featured explicitly in the conversation.  As is usual, we had a surplus of excellent ideas that could be implemented to improve the business.  The team debated themselves and started to form their own discipline as to how they focused on only the best ideas that will contribute to the strategic goals and move the needle discounting some valuable suggestions which we kept a note of.  This was not an easy session with signs of hostility and frustration occasionally being evident.  It concluded as a work-in-progress with some detail yet to be finalised.  </span></p><p><span style="font-weight: 400;">BENEFITS</span></p><p><span style="font-weight: 400;">At the end of this phase the leadership Community as a whole across the Enterprise from the CEO to the most junior line manager had a consistent and collective understanding of the business strategy. This brought together the leadership community in an aligned cohesive way such that they had a reinforced understanding of the business’s reason for being and its future plans, clear to all those who own targets or metrics which will determine in large part the business success.</span></p><p><span style="font-weight: 400;">The leadership community spent quality time together and improved their interpersonal relationships.  Trust increased, vulnerabilities were exposed,  constructive conflict was encouraged, and accountabilities were made clear &#8211; with lots of smiles and some fun being had too!  Personal preferences, behavioural styles and ways of working were demonstrated across the team in a safe and positive environment, recognising (sometimes for the first time ever), the diversity of skills and personalities in the room.  These experiences are fundamental in developing high performing teams and by creating an environment where this has been practised,  everyone is now equipped with the process and structure to continue their journey &#8211; if they wish.    </span></p><p><span style="font-weight: 400;">A bunch of stuff was created to be used as consistent collateral to onward communicate,  to use as baseline source data, and maybe most importantly as a North star around which the organisation can focus its efforts.  Tangible and physical outputs from this process are also important to show to the wider population explaining what the leadership community has been doing together, why it is important, and probably most importantly what it means for them, which alone has also been shown to improve working relationships,  engender greater trust, bring clarity and focus, and improve retention. This phase as a standalone exercise measurably improves the performance standards of the team and ensures solid foundations on which to build the future.</span></p><p><span style="font-weight: 400;">Finally,  let’s not forget that it is perfectly possible that the change journey the organisation is pursuing may not be for some people.  Creating the environment where colleagues may choose a different path either within or outside the organisation often provides a cathartic experience for all concerned.  </span></p>								</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				</div>
		]]></content:encoded>
					
					<wfw:commentRss>https://leadersprotocol.io/leaders-protocol-methodology-phase-2-case-study/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Leader’s Protocol Methodology: Phase 3 Case Study &#8211;  Trust Based Commitment</title>
		<link>https://leadersprotocol.io/leaders-protocol-methodology-phase-3-case-study/</link>
					<comments>https://leadersprotocol.io/leaders-protocol-methodology-phase-3-case-study/#respond</comments>
		
		<dc:creator><![CDATA[Peter]]></dc:creator>
		<pubDate>Mon, 12 Jun 2023 07:31:21 +0000</pubDate>
				<category><![CDATA[Case Study]]></category>
		<guid isPermaLink="false">https://leadersprotocol.spectrawebdesigns.co.uk/?p=1054</guid>

					<description><![CDATA[To create sustained velocity and progress, creating an environment that emanates ownership, accountability, and fundamentally trust between leaders becomes an immense differentiating competitive advantage. Enthusiasm was high at this stage and for a number of reasons.  Some wanted to get this process out of the way so they could just get on with their work [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1054" class="elementor elementor-1054" data-elementor-post-type="post">
						<section class="elementor-section elementor-top-section elementor-element elementor-element-1094378 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="1094378" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-893cfcc" data-id="893cfcc" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-d0640eb elementor-widget elementor-widget-heading" data-id="d0640eb" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-medium">To create sustained velocity and progress, creating an environment that emanates ownership, accountability, and fundamentally trust between leaders becomes an immense differentiating competitive advantage.</h2>				</div>
				</div>
				<div class="elementor-element elementor-element-1a629f0 elementor-widget-divider--view-line elementor-widget elementor-widget-divider" data-id="1a629f0" data-element_type="widget" data-e-type="widget" data-widget_type="divider.default">
				<div class="elementor-widget-container">
							<div class="elementor-divider">
			<span class="elementor-divider-separator">
						</span>
		</div>
						</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				<section class="elementor-section elementor-top-section elementor-element elementor-element-83747c6 elementor-section-boxed elementor-section-height-default elementor-section-height-default" data-id="83747c6" data-element_type="section" data-e-type="section">
						<div class="elementor-container elementor-column-gap-default">
					<div class="elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-7876bea" data-id="7876bea" data-element_type="column" data-e-type="column">
			<div class="elementor-widget-wrap elementor-element-populated">
						<div class="elementor-element elementor-element-7f278c8 elementor-widget elementor-widget-text-editor" data-id="7f278c8" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">Enthusiasm was high at this stage and for a number of reasons.  Some wanted to get this process out of the way so they could just get on with their work &#8211; that’s fair enough, but everyone had to be on the same page and collective understanding is critical.  Some enjoyed the process as a cathartic experience, shedding a lot of frustration or learning something or just getting to know colleagues a bit better.  It all makes for a constructive working environment for me!  So, how were we going to do this? The rubber hits the road and we need to demonstrate:</span></p><ul><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Creating momentum with tangible outcomes</span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Understanding what&#8217;s working and what&#8217;s not </span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Knowing who’s accountable for what </span></li><li style="font-weight: 400;" aria-level="1"><span style="font-weight: 400;">Making sure the environment is conducive to learn and progress </span></li></ul><p><span style="font-weight: 400;">Engagement was vital throughout this stage.  The targets are devised and owned by the team, they are not “done unto”. So the whole process of “making progress&#8221; must be relevant and authentic to the people who are doing the heavy lifting.  Any “Going through the motions” at this stage is potentially fatal. </span></p><p><span style="font-weight: 400;">Placing bets </span></p><p><span style="font-weight: 400;">The appetite in the room for success was really positive, along with a sense from the team leaders of “We’ll prove we’re right” about their leading indicator choices or as we called them “bets”.  We dedicated a session to how progress would be measured by whoever owned the metric.  This proved to be a challenge.  In no time, we had a multitude of measures &#8211; on reflection everyone involved in the particular target wanted a measure that they related to best.  That meant many measures for one target.  A guiding principle of this part of the process is that the measure has to be something those delivering it can rally around and know exactly how they’re doing. It does not mean that is the only measure that matters, but it&#8217;s the only one that matters to them.  Getting people to place bets on their actions can cause a lot of looks around the room … “You go first”, “No, after you!” I was asking people to effectively say “If I do this, then I predict that will result in xyz” (where xyz is a company goal &#8211; invariably, almost always a lag measure, which means by the time you know if you’ve achieved it, its history.  The openness of the team to share their concerns was admirable. In essence, “I’m going out on a limb here, I may be wrong. I don’t want to get thrown under a bus if I am!”  Rationally, the benefit of leading indicators is that you can tweak your hypotheses and bets as you see the effect of what you&#8217;re doing, so this helps mitigate the problem.  Emotionally, things were a little different.  People were being asked to own their measures &#8211; the choice of measure, the performance standard, and explicitly know and understand how their decisions contributed to the company strategy.  That’s a big change curve to navigate and quality time was given to reinforce the team ethos and the trust that could only be proven by taking the actions being discussed.  A real case of something being simple, not easy.</span></p><p><span style="font-weight: 400;">The leadership team wanted the people most familiar with the target areas to contribute to the areas of focus, goals, and measures.  When we covered this in a face to face session, the perception was apparent that this was an empowering experience; employees were afforded the opportunity to decide for themselves what measures mattered to them to help achieve a higher order strategic goal.  In other words targets weren’t being forced on them &#8211; they got to decide.  This was well received! We raised the point that with empowerment comes accountability &#8211; that is &#8211; this is what you think is required; that the CEO trusts and believes you; will support you in achieving the targets you’ve proposed; and will also hold you accountable to meet them.  We’d worked on trust in previous sessions and nonetheless, the reality of the CEO’s accountability message took us time to just chew through and appreciate how that changed things.  </span></p><p><span style="font-weight: 400;">Placing bets relates to lead measures, for example, in a call centre, if I answer calls faster today, customer satisfaction will increase tomorrow.  Lead measures can adapt as time passes whereas lag measures usually never do.  Lead measures need subject matter experts to formulate them. You’ve got to be up close and personal with the data, understanding the customer, product, code, whatever &#8211; and that’s where line managers over C-Suite invariably excel.  So our workshopping involved getting engagement to own the target, really demonstrate a collective understanding of it, and then bet on it as a leading measure to drive business success.  </span></p><p><span style="font-weight: 400;">Devising the target is invariably a lengthy messy conversation that needs to be distilled into very succinct metrics.  An appearance from the COO dragged the discussion into C-Suite language &#8211; not helpful at this point because we were simply re-wording existing lagging indicators with different words.  Similarly, each participant in the room had views they dearly held. Finding collective agreement on key leading measures was hard and I couldn&#8217;t have asked for more as these people worked at finding them &#8211; with trust and openness, support and challenge.  To use a sporting analogy, watching an international rugby test match today, you’ll see the coaching team throughout the match, hunched over laptops being fed streams of real time data, all of which is very useful … to them!  The supporters on the other hand want to see the score, that&#8217;s the data point they’re most interested in.  Occasionally the TV screen will flash up some supplementary data that may be relevant at that moment based on say the commentator’s narrative, but it&#8217;s fleeting only and relevant to a moment in play. </span></p><p><span style="font-weight: 400;">PLAYING TO WIN</span></p><p><span style="font-weight: 400;">Being exposed to the “score” prompts engagement, understanding, and awareness of the measure.  It also informs if the actions are actually working.  We broke into sub groups for this session, based on various leading indicators that had been agreed.  The groups were the metric owners and were tasked with coming up with their own means of measuring and tracking &#8211; that was entirely focused on those who would be delivering the work, no one else.  They are the most important and relevant audience for this very specific data.  How that feeds up into other targets and metrics is not important right now &#8211; the team leaders were wholly focused on how they could serve those doing the actual work with information that helped them deliver pretty stretching targets &#8211; that they had formulated and agreed.  This session brought with it great levels of transparency, authenticity, and humility &#8211; for example, some pertinent details were not known by anyone in the room and that was openly admitted  by individuals and also accepted by colleagues without criticism, with a collective acceptance of there being a gap in knowledge that needed to be fixed.  The team was now in a Playing to Win mode.</span></p><p><span style="font-weight: 400;">In this example, the team concluded measures and targets that meant that the subscription service after certain other criteria had been met and client satisfaction was understood. This meant delaying revenue streams.   To date they have a 22% increase in subscription take up.  So is that causation or correlation?  That is open to conjecture, but what they have done is make sure that those closest to the situation to bet on what would make a positive effect &#8211; and incentivise them to do so.  </span></p><p><span style="font-weight: 400;">KEEPING SCORE </span></p><p><span style="font-weight: 400;">As with many busy teams, wanting to use their time to talk about “Governance” didn’t land well! I try to adopt the idea of JBEP or “Just Barely Enough Process”, because whilst lots isn&#8217;t usually needed, some is. I strongly believe that it&#8217;s worth having a little and using it effectively &#8211; centred on the teams who have to use it and worthwhile for the people who need it. We agreed on that basis to work on governance!</span></p><p><span style="font-weight: 400;">We workshopped what we could tweak to make sure that progress was tracked, data was analysed, adjustments were made in a timely way, and above all communication was rock solid. </span></p><p><span style="font-weight: 400;">Everything was either adapted or created by the folks who would be using it, emphasising the notion of ownership &#8211; you placed the bets, you created the measures, you record your achievements.  Their scorecard was an important communication tool for their teams and the C-Suite so getting it right was something that as the session went on became very evident. </span></p><p><span style="font-weight: 400;">COMING TOGETHER</span></p><p><span style="font-weight: 400;">Being trusted to work with a leadership team’s line managers is something that I hugely respect.  The satisfaction of seeing the line manager community meet with the C-Suite to present back their plan as to how they will deliver the execution of the strategy is a great experience.  It doesn&#8217;t tend to go 100% smoothly and there are compromises that have to be resolved &#8211; which I see as a good thing.  In this case, some fairly minor tweaks were made, mainly to sequencing and timing.  The most positive thing I observed as an outsider was a group of people who had belief, trust and confidence in each other, well placed to further evolve and thrive taking their business forward. </span></p>								</div>
				</div>
					</div>
		</div>
					</div>
		</section>
				</div>
		]]></content:encoded>
					
					<wfw:commentRss>https://leadersprotocol.io/leaders-protocol-methodology-phase-3-case-study/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
