<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by adam lenander on Medium]]></title>
        <description><![CDATA[Stories by adam lenander on Medium]]></description>
        <link>https://medium.com/@adamlenander?source=rss-7d77872b544------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TP9-CP1t0T8_iQjTN8g1Vw@2x.jpeg</url>
            <title>Stories by adam lenander on Medium</title>
            <link>https://medium.com/@adamlenander?source=rss-7d77872b544------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:27:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adamlenander/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[“BHAD” — Brutally Honest Agile Dictionary. For Seasoned Users Only…]]></title>
            <link>https://adamlenander.medium.com/bhad-brutally-honest-agile-dictionary-for-seasoned-users-only-c49a07959631?source=rss-7d77872b544------2</link>
            <guid isPermaLink="false">https://medium.com/p/c49a07959631</guid>
            <category><![CDATA[humor]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[adam lenander]]></dc:creator>
            <pubDate>Sun, 23 Feb 2025 13:53:27 GMT</pubDate>
            <atom:updated>2025-02-23T13:53:51.342Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>“BHAD” — Brutally Honest Agile Dictionary. For Seasoned Users Only…</strong></h3><p>Something a bit more lighthearted to prick the egos of all of us involved in making change happen……</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vQyzJv78t4HKXx8VTtSj6A.jpeg" /></figure><p><strong>Agile Coach</strong> — Someone who either knows too little and is therefore dogmatic and irritating, or knows to much and is an alcoholic (see <em>Story Pints</em>). Borderline sanity/manic depression is a defining feature</p><p><strong>Agile Couch</strong> — Comfy seats in corner of office otherwise filled with soulless rows of highly packed, regimented desks. Only purpose is for carefully positioned photo shoots to show a modern office</p><p><strong>API</strong> — allegedly painless interface — a wonderful idea whereby you can ask for data and have it provided. A great idea as long as you can find one. Or the team that owns it. If not the usual approach of building a bespoke data link to a non-golden data source as a <em>stractical fix</em> is always an alternative. Often used by non tech people with no understanding of the underlying ideas (see <em>blockchain, big data, IoT)</em></p><p><strong>Architect</strong> — A once talented and thoughtful developer who got tired of writing code but likes to still be seen as more important than the masses</p><p><strong>Backlog</strong> — The never ending story of what were once passing ideas now forever encapsulated as Jira items that not only will they never be deleted, but even if they are they will be retained for 7 years as part of the data policy. This means that Jira tickets have longer tenure than most employees</p><p><strong>BDD</strong> — Badly Described Demands — A powerful tool that people cant be bothered to learn. Normally used as a way to not only not clarify fully the needs of the user, but also sneak in technical design decisions and hamper the product from the start</p><p><strong>Big Data</strong> — a wonderfully vague description of a database that for a time was seen to add credibility to any funding application, strategy document or <em>conference engineers </em>presentation. Quietly fading away as we only care about AI now….</p><p><strong>Blockchain — </strong>A classic example of a solution looking for a problem, this has been one of the most outstanding successes in creating massive fraud, environmental destruction and market manipulation. But it fantastic way to support critical areas of the economy such as <em>conference engineers </em>and the paid-for awards industry</p><p><strong>Business Value</strong> — A mythical means to determine priority of items in advance, especially useless in companies with little to no direct customer engagement. Often used as a proxy to properly understanding complex trade offs, it allows the cerebrally challenged to quote “Business Value” to get pointless pet projects worked on instead of boring stuff like cybersecurity or deployment automation</p><p><strong>Clean</strong> <strong>Code</strong> — Where OCD meets impracticality, a way to create never-ending debate about the granularity of functions and naming conventions rather than outcomes. See <em>Ego</em></p><p><strong>COBOL</strong> — The last language written that was readable by non technical people. This has ensured it will continue for perpetuity, and knowledge of this is the greatest job security any developer could wish for. The fact the worlds financial systems continue to be dependent on this tech is terrifying — its like choosing to have the worlds nuclear arsenals in the hands of megalomaniacal senile old men….</p><p><strong>Conference Engineers</strong> — small cliche of touring speakers who espouse great sounding but overly complex solutions to problems you don’t need to solve, or could be fixed by simply talking to your colleagues. But hey, those air miles don’t pay for themselves</p><p><strong>Conway’s Law</strong> — amateurs believe this law helps guide the design of team structures to optimise the product architecture. Instead it should be seen as a fantastic means to understand ball of mud, god-awful applications with impenetrable code bases. Simply step back, look at the team structures (or lack of) and the lack of clarity of vision and hey presto! Now the labyrinthine architecture make perfect sense!</p><p><strong>Culture</strong> — This is the stuff of thousands of well meaning books, all espousing how the right one will transform your workplace. A classic quote is ‘Culture eats strategy for breakfast’. Well there is one common culture to trump them all — and that is <em>Politics.</em> Politics not only eats Culture for breakfast, it then claims it as a success and gets a promotion as well.</p><p><strong>Data Driven Decisioning</strong> — in an ideal world, enlightened people seek data to check if their efforts actually have delivered value, and make informed decisions off the back of what it reveals. This is clearly an insane idea when confronted with entrenched <em>Politics </em>and <em>Culture</em></p><p><strong>Definition of Ready</strong> — In a vain attempt to actually drive some minimum level of quality into the book of work and development process, scrum masters will often try and encourage teams to agree what good looks like. This clearly requires focus on outcomes and it is therefore to be strongly discouraged as this will lead to other foreign concepts such as outcome over outputs, and facts over opinions</p><p><strong>DORA</strong> — Way of getting a group of seasoned professionals to make noises like those on a children’s animation by introduction the concept of data driven management e.g. “Oooooo”, “Ahhhhh”, and “Ehh?”. The best way to use DORA metrics is badly — use a custom alternative that shows you are elite even as your production services are in meltdown after the quarterly release process and claim success</p><p><strong>Development</strong> — A wild arena of creativity and destruction, clarity and confusion with a sprinkling of talent and mediocracy. The best bit is university does nothing to prepare you for what you face when “Big Jeff” the grumpy 50 year old cynical dev ravages your attempts to do the right thing on the first attempt (see <em>Ego</em>).</p><p><strong>Domain Driven Design</strong> — a subset of <em>Conference Engineering</em>, this is another concept the in theory sounds great, despite the core idea failing at first contact with corporate reality. DDD has a place in the organisation however, as it can be transformed into a subtle way to ring-fence a number of applications when teams are tired of the corporate politics. If those teams are then challenged about performance in their area they can point to a random document based on this idea and confidently you to go take a walk as its none of your business…..</p><p><strong>Ego</strong> — or “Expression of Godlike Opinions” — Way to avoid learning, introspection and work by telling others they’re inferior and sticking to what you learnt 10–15 years ago in a rapidly changing industry</p><p><strong>EUC</strong> — End User Confusion — mistaken belief that the provision of IT services to employees is aimed at providing the best possible service. In reality it is a dark joke where the EUC team get to play will all the cool new tools ‘as a trial’ then decide no-one else is worthy of access. In the meantime the technology used by everyone else is a fragmented mess that lags 10 years behind what’s available for free on consumer devices</p><p><strong>Excel</strong> — the cause of and answer to most of the worlds problems. When Puritans campaign against the demon drink, they are focused on the wrong target, as addiction to Excel is far more destructive and way more persistent than a hangover.</p><p><strong>Executive Summary</strong> — High level detail that is primarily designed to fit a given amount of slide real estate rather than impart enough knowledge to help drive meaningful decision making</p><p><strong>Features</strong> — Barely thought through collector of wants that may or may not meet a specific need aside from being a way to maintain the Jira hierarchy. Linkage to a customer demand is a bonus</p><p><strong>IoT</strong> — Internet of Things — never before has a description been so accurate. This addition to ‘<em>Buzzword bingo’</em> literally includes ’things’ as a nod to the fact that nobody actually knows what this really means apart from the fact that sales and marketing insist on bluetooth in every device. The new connectivity is a nightmare of security holes and embedded code making future developers task impossible. But it sounds cool — until you need to upgrade the software on your kettle. Or fridge.</p><p><strong>Java</strong> — Java is a great coffee, a beautiful island, and erm, a very widespread language. It is capable of coding anything, which means in reality it is often used to do a vast amount of things badly. But hey, if it ain’t broke, don’t fix it! Sheeez it broke….</p><p><strong>Kanban</strong> — Rarely used well, it instead is often used as a way to abandon any form of structured way of working and give yourself over completely to the dark forces of chaos. Why limit WIP when there’s so much to do? Instead keep on starting tasks then complain Kanban doesn’t work. Much better!</p><p><strong>Learning and development</strong> — Theoretical use of company resources aimed at improving individuals skills. In reality a contingency pot for making up shortfalls in the budgeting process (see <em>QBR</em>)</p><p><strong>Language</strong> — There are many languages used in software development. The most interesting language is experienced during a catastrophic big bang release, which is inappropriate for repetition and would disappoint their mothers (see <em>Release</em>)</p><p><strong>LeSS </strong>— the industrialised version of <em>Kanban</em>. Though intellectually sound, this is also its biggest problem, as successful implementation requires people to think. Bad call.</p><p><strong>Lied time</strong> — Wild stories made up on spot about how long something will take. Initial creation does normally not involve anyone actually tasked with the build (see <em>QBR</em>)</p><p><strong>Low Code Solution</strong> — Excel. Where non coders chafe at paying the cost of doing things properly, Microsoft has the answer to hack your way to an unsupportable sticking-plaster solution</p><p><strong>Memeory</strong> — Key skill in being able to recall the right meme quickly to make fun of the current situation</p><p><strong>Microservices</strong> — A very clever way to mange complexity in large system architectures. Most commonly a way to introduce complexity into simple architectures, but the team wanted to do it because it’s ‘cool’ and looks good on a CV. Plus they will be using that CV to escape before having to support the monstrosity that results</p><p><strong>Mttr</strong> — Abbreviation of ‘mutter’, in other words the constant cursing of developers by testers or prod support as they have to once again pick up flaky, poorly written code (see <em>Production</em>)</p><p><strong>OKR</strong> — Objectionable Kafkaesque Requirements — This arises when a controlling, fixed-mindset budget process subsumes the language of agile planning approaches to create a Frankenstein”s monster of empowered language and 100% commitment years in advance wedded to consequence management</p><p><strong>OpCo / SteerCo</strong>- Means of having an official way to have a governance process with no decisions or personal responsibility for outcomes. Fantastic way to justify salaries of people not helping improve the working lives of delivery teams</p><p><strong>Oracle</strong> — No nothing like The Matrix. Think big, expensive infrastructure keeping Larry Ellison obscenely rich</p><p><strong>Open Source (OSS)</strong> — the only thing more scary than <em>excel</em> as a foundation of the world economy is realising that 70% of software is based on languages maintained by volunteers. As this means that there is no sense of ownership (I.e. profit) this means many companies don’t see a need to invest in supporting the communities keeping them in business. Awesome.</p><p><strong>Operations</strong> — Group of people who have the dual identity as being critical for filling in for code deficiencies, whilst being unimportant when it comes to influencing the product — despite usually being the most active users of the software. The unloved ginger stepchild of the product development process.</p><p><strong>Politics </strong>— this is the only way to guarantee advancement and a career, as opposed to naive ideas such as ‘delivering value’ or ‘knowing what you are talking about’. See <em>Culture. </em>Politics is the art of being seen as associated with success (real or imagined) rather than failure (all too real), and actually having to do work is a terrible impediment to the important task of focusing on politics. This is in direct conflict with <em>Data driven decisioning</em></p><p><strong>PowerPoint </strong>— job creation application that is a badly spot welded combination of a poor graphics editor, annoying text editor and severely limited animation tool. Though unable to do anything well it survives by being bundled with <em>excel </em>and by keeping millions of people in important sounding jobs busy, without actually delivering value. To this end it is by far the worlds most effective means of planning as it allows for no version control, live updates or holding people to account — I mean how many old meeting presentations do you re-read…?</p><p><strong>Prioritisation</strong> — Extremely dangerous concept requiring decisions to be made and stuck to, opening up people to repercussions resulting from making a choice. To be avoided wherever possible due to threat to career from having to prove competence and inevitably upsetting people with reality</p><p><strong>Project manager</strong> — Highly paid PowerPoint expert applying simplistic approach to keep bosses happy in spite of decades of evidence showing they only make things worse. Worse thing is the good ones know this and resort to <em>Story Pints</em>, the bad ones think they actually add value</p><p><strong>Product Owner </strong>— Normally a retitled project manager or BA, who is given a days training if lucky, but no empowerment to make a real difference. Something to be put up with for as short a time as possible just to burnish your CV. Often has limited interest in how the product actually works technically as that’s hard</p><p><strong>Production</strong> — The area everyone complains about paying for when working, but then complains even more about when it doesn’t</p><p><strong>Pull request</strong> — What developers try inappropriately in a bar after too many <em>Story Pints</em></p><p><strong>QBR</strong> — Quickly Bury Reality — A new form of the budgeting rain dance, where the fundamental rule of ignore negative feedback is just as strictly enforced. This allows all blame to be directed downwards without the responsibility of making required tough calls being accepted</p><p><strong>Red Green and CYAN</strong> — Stages of reaction to plan — red meaning people are angry about the stupid imposed delivery schedule, green is the rising feeling of sickness in stomach as they progress through a death march of weekend releases whilst the bosses have time with family, and CYAN (Cover Your Ass Now) kicks in when it inevitably goes wrong</p><p><strong>Refactoring</strong> — A theoretical process to ensure code is a good and as easy to understand as possible. Given this has to compete with new feature delivery, this goes in the same “nice to have” bucket as bringing about world peace, ending world hunger and a decent ending to Game of Thrones</p><p><strong>Release</strong> — A process to describe letting go of the shitty underdeveloped product and passing it to production. The internal pressure and short term relief this brings is undeniable, but there will be a god-awful mess to clean up afterwards. A bit like the the morning after too many <em>Story Pints</em></p><p><strong>Retro</strong> — Clothing worn by a subset to developers that even other developers refer to as ‘special’</p><p><strong>Roadmap</strong> — Plans for a coast-to-coast fly-drive holiday that will be cancelled due to project delays</p><p><strong>SAFe </strong>— or ‘how to sell agile to project management’, it is a case study in the creation of a new dogma and then profiteering off it. Though not having any successful use cases, it has infested the world of agile to try to make itself indistinguishable and suck people in. Once in, you will then need to keep paying SAFe $1,500 to maintain your ‘certification’ when they decide to change the wording of an obscure paragraph which has no impact on business delivery success. Nice</p><p><strong>Scrum </strong>— Schedule Complex Roster of Unnecessary Meetings — A great way to keep the project management mindset alive at team level whilst professing to be following the principles of highly productive development practices like XP. Allows all teams to march in lockstep like a great mass of unthinking resources that matches the planning assumptions</p><p><strong>Scum master</strong> — When all the unwanted unpleasant tasks are dumped on one poor sod whose opinions on improvement are ignored</p><p><strong>Serverless</strong> — A wildly overcomplicated solution for almost all problems that will be implemented anyway as it is “cool”, “we have dedicated cloud spend” or because people want it on their CV</p><p><strong>Sorry points</strong> — Desperate attempt to ignore reality of software and use project management tools at team level and predict precise timings for a fundamentally creative and non predictable process.</p><p><strong>SRE</strong> — Shift Responsibility Elsewhere. A way for a development team to move all blame for how the code actually runs to another team. Seems like a great idea initially when faced with poor production performance, but usually supports avoidance of ownership. Makes for interesting arguments</p><p><strong>Story Pints</strong> — The inevitable overindulgence in the local bar after (or even during) work in an attempt to reconcile the reality of your existence with your needs as a human. Can also be the reason for, and answer to, all future problems if an architect is present. Coping mechanism for teams drowning their sorrows due to poor working practices</p><p><strong>Stractical</strong> — Result of when teams implement an awful temporary fix to meet an unreasonable deadline that never get revisited. This creates a Frankensteins monster of an almost unsupportable mess that is hard to change and delivers an terrible experience. One of the most common application categories. See <em>Excel</em></p><p><strong>TDD</strong> — Tried, Despised, Dumped — Process of knowing your code actually does what is intended. As this requires people to actually think and address their flaws, it is better ignored than adopted (see <em>Ego</em>)</p><p><strong>Teiam</strong> — Proving that in fact there can be an ‘I’ in team, especially when not co-located or full of egos</p><p><strong>Throwput</strong>- Chucking stuff as fast as possible into production where it will still be unused — but at least the plan was met (see <em>QBR</em>)</p><p><strong>TPI</strong> — Officially: Total Performance Indicators — reality: Top People’s Income — Annual process aimed at suppressing income of most workers so that the executive bonuses are guaranteed irrespective of performance</p><p><strong>Tribe Lead (ART Lead)</strong> — The figurehead of a delivery area, whose main job is to attract attention and stand out from the rest of the Tribe. Often hoped to be a path to promotion, but the path can be treacherous. As per their namesakes on sailing ships, they are inevitably the first casualty when conflict ensures after things go wrong, usually being shot to pieces from all sides when political warfare commences.</p><p><strong>Waterfall</strong> — Despite being discarded at the dawn of software development as singularly inappropriate for the task at hand, it is now the dominant management methodology. It has proven to be useful as it ignores the complex reality of the task in hand and replaces it with pretty slides that make everything seem simple. In this way it is similar to newspaper horoscopes — utter nonsense and forgotten the next day and with no impact on solving the issues faced in the real world</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c49a07959631" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3. The DADA Loop — How To Improve Decision Making In Organisations]]></title>
            <link>https://adamlenander.medium.com/3-the-dada-loop-how-to-improve-decision-making-in-organisations-9834027a786f?source=rss-7d77872b544------2</link>
            <guid isPermaLink="false">https://medium.com/p/9834027a786f</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[continuous-improvement]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[adam lenander]]></dc:creator>
            <pubDate>Sun, 02 Feb 2025 19:52:34 GMT</pubDate>
            <atom:updated>2025-02-02T20:33:52.367Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>3. The DADA Loop — How To Improve Decision Making In Organisations</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*JWLF1DXgImc_r5fb3-fUkA.jpeg" /><figcaption>Knowing what decisions to take is becoming increasingly overwhelming as the pace of change intensifies</figcaption></figure><p>As the pace of change continues to intensify, there is relentless pressure to improve delivery effectiveness. Budget cycles bake in assumptions of performance uplifts, volume growth, operational savings or all of the above. This often results in a mass of KPI’s that may in isolation be well-intentioned, but can be overwhelming when they combine at the delivery level.</p><p>The problem with many of these targets is that they are applied from a position far removed from the reality of the teams having to ensure their implementation. This usually gives rise to a process optimised for ease of reporting by those central teams, which is problematic when these reports become the only management KPI’s steering the organisation. The result is often turning what should be a continuous improvement mindset into a mass of separate KPI mini-projects chased up by different managers competing for attention.</p><p>This area is the remit of the Management Information System (MIS), an area surprisingly often overlooked due to a focus other reporting requirements — accounting, environmental, HR, etc. These reports are clearly essential to meet legal obligations, but they serve a different need than those required for a comprehensive MIS. Accounting cycles for example are slow and often produce numbers that have been manipulated to meet standardised financial requirements making them of little use to the management of continuous improvement processes.</p><p>To be effective MIS must alert management when a problem has occurred. To do this, systems should use actual performance to distinguish between activity that is productive, non-productive, or when no activity has occurred. An effective MIS will provide a continuous monitoring through the complete cycle from forecasting, planning and delivery, allowing rapid feedback and intervention. By providing this continuous cycle, teams are able to see whether the decisions they have made have been effective.</p><p><strong>Differences between fixed outcome and continuous improvement systems</strong></p><p>Fixed outcome measures are common as they present a simple model and allow for basic reporting. These reports assume that a fixed and pre-determined solution will deliver the needs of the business. A valid example would be an audit closure tracker, where once a defined action has been validated, the point is closed. The danger is fixed measures are often reductionist in their assumptions, acting to focus the organisation on task completion rather than provable outcomes. For example, if an audit point action does not actually remediate the issue, this can trigger a conflict over closure of the KPI (wasteful infighting) rather than using this as a learning opportunity for the organisation (risk reduction).</p><p>Continuous improvement approaches instead rely on a robust feedback mechanism. This allows the testing of ideas and a change in approach when needed. These systems do not assume the selecting the perfect next step, but instead on rapid feedback to determine success and speed up the learning process. This is the basis of truly effective decision making, and is where the Data-Analysis-Decision-Action (DADA) loop comes in.</p><p><strong>Data — Analysis — Decision — Action:</strong> <strong>The DADA loop</strong></p><p>This loop is needed at all levels of the management structure to provide the timely feedback and self-correction mechanism for decision making. The approach is equally valid whether applied to external facing functions e.g. forecast vs. actual sales, or internal processes e.g. required vs. actual delivery performance. The DADA loop is deceptively simple as a concept, but making it function effectively is one of the distinguishing features of world class organisations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nvv1h69g0JNKbrA40-WY0A.jpeg" /><figcaption><em>The DADA loop as presented in </em><a href="https://www.google.com/url?sa=t&amp;source=web&amp;rct=j&amp;opi=89978449&amp;url=https://www.youtube.com/watch%3Fv%3D1Jo7mDv4jjs&amp;ved=2ahUKEwjal568zKWLAxUzR_EDHQ4dOcwQtwJ6BAgPEAI&amp;usg=AOvVaw3zeQ3MwBaBvxdUdFqfBhvr"><em>my talk at the SEACON conference in November 2022</em></a></figcaption></figure><p><strong>Data</strong></p><p>At the core of the feedback loop is the need for decisions to be validated by data — a process divorced from data is not a robust decision-making process.</p><p>Imagine being a passenger in an aircraft where the captain strolled around making some of the following statements. “I think we have enough fuel to make it to our destination” or “I always assume the weather is going to fine”. You should feel nervous! You would probably feel that many of the decisions concerning your safety were being made on unreliable data. Similar situations occur in companies concerning tough decisions or trade-offs. To be competitive today means managing the business on readily available facts — not perceptions based upon “experience”.</p><p>Many companies actually suffer from too much data. Deciding which data to collect is not judged by volume or ease of availability — rather it has to be judged by the quality requirement and needs of the organisation. Relying on junior team members whose main skill may be proficiancy with a data visualisation tool is foolish — the changes needed to allow rapid feedback can be impacted by in governance and control processes, management structures and regulations. This is core responsibility of the mmagement team to address and implkement.</p><p>Any operation can be regarded as having two major focuses. There is a process itself and there are the people who support the process. Data is required both on the process element because this reflects the result of the activities of the supporting function, and of the people element because this indicates how and why the process has performed as it did.</p><p>The amount of work planned will always be a key piece of data. This is the work that was considered to be necessary in order that the process could have performed at optimal efficiency. The amount of actual work achieved is of interest because this will indicate whether the plan was not achieved, met or exceeded (see previous posts on overcommitment for the risks this creates).</p><p>The demand and the availability of skills will be another key data point, as the demands on the workforce inevitably<em> </em>evolve over time. This data should be tied to hiring, training and personnel improvement plans.</p><p><strong>Analysis</strong></p><p>Data collected around the parameters previously mentioned will not be meaningful to management and supervision. They need to see trends and variances and it is here that effective systems carry out a vital function. Effective systems translate data, via analysis, into trended Key Performance Indicators</p><p>The stage of analysis takes raw data and transforms it into information so that management may quickly and easily identify both trends and variances from the desired performance. The analysis process in the DADA circle creates clarity from a mass of data.</p><p>For example, plan attainment helps improve the forecasting process by comparing it to what was actually achieved. Quality measures are an obvious choice if we wish to attain a “get it right first time” culture. In production systems, Mean Time to Repair would give an indication of whether planned times were being achieved and would also indicate what influence maintenance might have upon the production systems availability.</p><p><strong>Decision</strong></p><p>Given a firm base of data and an effective analytical process, decision making becomes more predictable. Management is able to address quantified problems, and the predictability of possible improvement can then be forecast accurately. This does however need enough psychological safety for people to act on the analysis no matter where that may lead. For example, it can be tough to abandon a product that is not delivering, or a previously selected solution that is not meeting requirements, if this choice will leave the team feeling exposed.</p><p>The system will support management in that it will identify the source of the problem. For example, a robust system will identify that a certain proportion of capacity is being lost due to an activity. This does not take away the need for management and technical expertise necessary to identify why that is the case. It allows management and technical expertise to be focused more effectively, and to make a timely decision.</p><p><strong>Action</strong></p><p>An area which constantly identifies world class performers is the ability of the organisation to drive home decisions by turning them into actions. World class performance means having the ability to make things happen.</p><p>Although the process is not complex many companies fail to master it. What needs to be done — who will do it and when will the actions be completed? The secret of success is to break the action down into detail and to have systematic reviews that takes place frequently. In this way any off-schedule conditions can be corrected before too much slippage has occurred.</p><p>Clarity of communication and objectives is also a critical part of action delivery. What is the expected change we hope to see, and how will this be reflected in the data? This is where a rapid feedback loop becomes essential — as new data becomes available it allows the action effectiveness to be understood</p><p><strong>In Summary</strong></p><p>The circle is complete. The systems are designed to collect the data that will be required to make robust decisions which is then converted into trends and variances that help identify and quantify problems that occur. The system, if effectively designed, will aid the decision process — but the real secret of success is turning those decisions into concrete action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4vDTf8vXU6ZAkSmTXMByQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9834027a786f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2. Overcommitment at work: The role of leadership]]></title>
            <link>https://adamlenander.medium.com/1-overcommitment-at-work-the-role-of-leadership-817cdbeaf771?source=rss-7d77872b544------2</link>
            <guid isPermaLink="false">https://medium.com/p/817cdbeaf771</guid>
            <category><![CDATA[over-commitment]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[delivery]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[change]]></category>
            <dc:creator><![CDATA[adam lenander]]></dc:creator>
            <pubDate>Sun, 26 Jan 2025 17:16:20 GMT</pubDate>
            <atom:updated>2025-01-26T17:20:44.795Z</atom:updated>
            <content:encoded><![CDATA[<p>In my previous post I talked to systemic issues that can lead to organisations overextending themselves. The result is pressure to present progress in a positive light to secure advancement, or <a href="https://hbr.org/2023/02/what-is-psychological-safety">attempts to avoid blame for poor performance</a>. Both of these paths result in a similar outcome — an increasing separation of the way the organisation models the world from the reality on the ground. In this post I will focus on the role individuals and leadership play (both positive and negative) in setting and maintaining realistic expectations</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/451/1*O-L5VHZGDTqjAZWQMTybsQ.jpeg" /><figcaption>Leaders need to look to themselves for the reasons for overcommitment</figcaption></figure><p>Overcommitment in work can arise when there is a shift from the use of real-world feedback to purely subjective measures of success. The danger is this situation encourages distortions of messaging in the pursuit of individual aims — be it plans or schedules, financial reports or business projections. The need to maintain a consistent story also subtly discourages new thinking. Simple models, even if wrong, are easier to create and defend than those that allow for the ambiguity and complexity of delivery (I will cover this in a future post). Where this behaviour remains unchallenged or even rewarded, it becomes the default means of securing status and maintaining power within the organisational hierarchy. This is rational approach for individuals given that our status is such a key aspect of human societies.</p><p>The reality is this behaviour can always exist whenever the count of humans in a system is greater than zero. Are we always honest with ourselves when we miss our goals or make promises of action? Are we really thinking through the impacts on others or expressing the problem from a purely personal viewpoint? This effect has to be considered as our lives play out in social constructs with needs, politics and status games.</p><p><strong>So what does this all have to do with overcommitment?</strong></p><p>Inexperienced or poor managers are less likely to consider these pressures as something to deliberately counteract. Instead of trying to c<a href="https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2022.921300/full">reate options for honest feedback</a>, they may avoid challenging conversations with those of higher status, pushing more demands to the teams below them instead. This can result in celebrating toxic behaviours such as an overloaded team constantly taking on more work outside the scope of their weekly priorities. Examples include end of year summaries routinely praising staff for their “commitment” after repeatedly being forced to work overtime, whilst having no time to maintain or learn new skills.</p><p>This lack of management effectiveness can quickly become normalised. Agreeing to unrealistic stretch goals beyond a reasonable scope can become portrayed as a sign of leadership ability rather than a failing. Overcommitters quickly lose sight of the fact that focus is a key means to delivering a quality outcome, and that value is derived from excellence in execution. Great client outcome is not the same thing as simply marking an output based milestone green and claiming success.</p><p><strong>So how can we escape the overcommitment trap?</strong></p><p>Firstly, this is not a quick fix. There are no easy answers otherwise this would not be a common issue. The increased pace of change means that there is always more work to do than there is time to do it, and this pressure will only increase. The answer is not found in unintelligent, throwaway lines like “Do more with less” or “Go the extra mile”, but in the tough choices and required actions to ensure the important things happen.</p><p>Any leadership unable to provide focus is messaging that it does not really understand what is important. This is why overcommitment is so toxic. It creates a culture where all demands are valid, overloads delivery teams and sacrifices quality. Teams view managers as incapable and trust erodes, as those same frustrated managers blame teams for lack of delivery to the plan. The organisation slowly loses focus on the outcomes (rather than excelling at them), drowning in work and creating unnecessary conflicts (due to incomplete dependencies and overlaps). As a leader, have you recently checked if the delivery teams within your influence are overloaded? If so, what concrete steps have you taken to resolve the situation?</p><p>This is not an academic point. These choices, or lack of them, directly affect all involved. People can end up miserable at work not because they were doing a bad job but because they took personal responsibility for things beyond their control. Plans become increasingly worthless, as it becomes apparent it is impossible to deliver on the commitment, but which portion that will be missed is unclear. <a href="https://youtu.be/75bO_XWk7fw?si=kx9hh3VNKGkqTwiM">This further erodes trust between different parties, increasing the risk of conflict</a>.</p><p>The role of leadership is to make decisions when needed, and only reason for overcommitment is that decisions have not been made. <strong>Repeated overcommitment advertises poor leadership more effectively than almost any measure.</strong></p><p><strong>Try taking a small step today to address it — be persistent, and be patient.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=817cdbeaf771" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[1. New year, new plans, new commitments]]></title>
            <link>https://adamlenander.medium.com/1-new-year-new-plans-new-commitments-ad305e48a240?source=rss-7d77872b544------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad305e48a240</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[overcommitted]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[adam lenander]]></dc:creator>
            <pubDate>Sun, 05 Jan 2025 15:54:52 GMT</pubDate>
            <atom:updated>2025-01-05T15:54:52.566Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*wnDr9IJ-zTLiXWNcv-ZrPw.png" /></figure><p>This is a time of year when many of us are in a period of looking ahead, both in our work and personal lives. On top of self-improvement resolutions to get fit, lose weight or do that thing we dreamed of doing, there are often annual planning cycles in work. As we step into the new year, we should be mindful of forces that can lead us into trouble unless we take time to think about our commitments.</p><p><a href="https://en.wikipedia.org/wiki/Planning_fallacy">Planning fallacy</a> can be trap that can arise due to individual or systemic pressures. We can be led into subjectively report positive views of reality; hold unrealistically positive expectations, views, and memories; and to favour positive information in reasoning. This can lead us to focus optimistically on highly visible goals (whether that is a new year’s resolution or delivery of a product) whilst discounting the impact of competing time pressures. The result is overcommitment — well intentioned, but unrealistic.</p><p>In our personal lives this can have negative effects on our own self-image or our relationship with others as we can perceive ourselves as a “failure” when we miss our goals. In work the effects can be just as damaging, and lead to dangerous, long-lasting changes in culture.</p><p>Overcommitment in work can arise when there is unintentional misalignment between expectations and the real-world performance of teams, or worse, a deliberate overriding of feedback in pursuit of personal goals. The former is often the result of poor information, communication or analysis (systemic failures), whereas the latter can be due to poor practices, decisions or incentives (management failures), though there can be extensive overlap of these drivers. I will focus on the former for now and cover the management aspects in a future post.</p><p><strong>The causes of decay in management systems</strong></p><p>Systemic failings can grow if there is a lack of attention given to actively fighting the tendency of organisations to become increasingly complex over time (<em>see </em><a href="https://en.wikipedia.org/wiki/Parkinson%27s_law"><em>Parkinson’s Law</em></a>). The increasing complexity splits responsibilities, encourages the formation of silos and creates locally optimised versions of what had been shared resources. This can make management information increasingly difficult or even impossible to obtain on a timely basis, reducing the use of such data and therefore feedback discouraging focus on maintenance and collection of such data.</p><p>This situation can persist as resolving this is also seen as ‘somebody else’s problem’ for all concerned. By its nature, information needed for daily operations spans multiple areas of responsibility and often has lower perceived value than data on costs, revenues, headcount etc. This is compounded by the fact that by the time the reporting lines of the areas overseeing a process come together, the seniority of the management is usually so high that they are not involved in operational data issues.</p><p>The net result is separation of planning from real world data, and so a shift from data-validated to status-validated plans. This is where demand is committed to separately from the actual ability of the organisation to deliver safely, and ignoring bottlenecks in the process.</p><p>The inevitable failures that result from this kind of continual planned overcommitment destroys trust across the organisation and in turn reduces productivity due to lack of focus and context switching. All plans are unreliable in this scenario, as it is impossible to deliver all asks in the proscribed timeframe. It is especially problematic when there are dependencies between teams, as a single missed delivery can have significant ripple effects. This feeds back into the planning cycle creating an environment based on distrust and local optimisation (either for a department or project) rather than collective prioritisation and optimisation. The effect can be to increase operational risks (plans unable to adapt to emerging issues, or a lack of focus on quality and resilience) and <a href="https://www.cio.com/article/657960/burnout-an-it-epidemic-in-the-making.html">chronic stress</a> (another significant driver of low productivity).</p><p><strong>So how can we escape the overcommitment trap?</strong></p><p>The initial step has to be to clearly prioritise work — <em>stop starting and start finishing</em>. Even in the absence of delivery performance measures, setting a clear priority allows focus and ensures the most important work is completed. This will of course mean tough choices to stop other items — but these would not have been completed anyway. Using this approach to <a href="https://www.seerinteractive.com/insights/context-switching-impact-team">reduce context switching</a> is the easiest way to increase productivity.</p><p>The second step is to <a href="https://flowframework.org/">measure delivery performance</a> and use this to set a limit for accepting work into teams. Over time this will raise confidence in planning and dependency management, and increase delivery performance. If this results in work being completed early, teams can move on to the next items — but a commitment once made to others cannot be undone without loss of trust and/or wider impact.</p><p>The final step is to ensure there is a mechanism to constrain complexity in the organisation, with an aim to ease of management data availability, quality and timeliness. This needs both an initial push to build missing capabilities, and an ongoing focus to counteract organisational fragmentation and complexity growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad305e48a240" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>