Archive

Monthly Archives: May 2022

A Conducive System

[Tl;Dr: What are the system conditions that encourage ethical – and productive, effective – behaviours (Cf William Kingdon Clifford) in software delivery organisations?]

In yesterday’s blog post “The System Is Unethical” I related my experiences of how businesses – and the folks that run them and work in them – remain ignorant of just how ineffective they are at software delivery. And the consequences of that ignorance on e.g. costs, quality, customer satisfaction, etc

To recap: an unethical system perpetuates behaviours such as:

  • Failing to dig into the effectiveness of the organisation’s software delivery capabilities.
  • Indifference to the waste involved (wasted time, money, opportunities, human potential,…).
  • Ignorance of just how much more effective things could be, with e.g. a change in perspective.
  • Bravado and denial when questioned about such matters.

The Flip Side

Instead of the behaviours listed above, we might seek a system that encourages behaviours that include:

  • Continual attention to the effectiveness of the organisation’s software delivery capabilities.
  • Concern over the waste involved, and actions to reduce such waste.
  • Investigation into just how much more effective things could be.
  • Clarity and informed responses when questions about such matters.

Conducive System Conditions

So what might a system conducive to such behaviours look like?

That’s what my book “Quintessence” illustrates in detail. But in case you’re a busy person trapped in a non-conducive system, I’ve previously written about some of the key aspects of a conducive system, here:

Quintessence For Busy People

BTW I’m always happy to respond to your questions.

– Bob

 

 

 

 

The System Is Unethical

Or at least, it’s “the system” that sits at the root of the unethical behaviours costing software delivery organisations £££millions annually. And it’s the culture of an organisation that defines that system.

Many years ago I wrote a White Paper titled “All Executives Are Unethical”. This paper riffed on a theme from Seth Godin – “All Marketers are Liars”. And channeled the ethical arguments of William Kingdon Clifford:

…whatever someone chooses to believe cannot be exempt from the ethical judgement of others.

In the aforementioned White Paper, I spoke of the ethics of executives, and in particular the folks that make the decisions about committing to improvements (or maintaining the status quo) in software delivery.

It’s been my experience over the course of thirty-plus years, that said executives act as if they believe their software delivery capability has little need, or scope, for improvement. Acting as if investing in improving said capability has little to no payback, and little to no impact on the organisation’ top line or bottom line.

It’s The System

Bill Deming famously wrote:

The fact is that the system that people work in and the interaction with people may account for 90 or 95 percent of performance.

~ W.E. Deming quoted in Scholtes, PR 1998 ‘The leader’s handbook: making things happen, getting things done’ McGraw-Hill, London p 296

Some readers of my aforementioned White Paper may have inferred I was criticising individual executives for their shortfall in ethics. Not at all. These folks work in “systems” as much as everyone else. It’s the system that drives their behaviours. Behaviours such as:

  • Failing to dig into the effectiveness of their organisation’s software delivery capabilities.
  • Indifference to the waste involved (wasted time, money, opportunities, human potential,…).
  • Ignorance of just how much more effective things could be, with e.g. a change in perspective.
  • Bravado and denial when questioned about such matters.

And it’s not limited to executives. Most advisors and practitioners (coaches, developers, middle managers, etc.) are equally ignorant, indifferent, flippant and slow to inquire.

Organisational Psychotherapy – and in particular, Memeology – offers a means to being addressing the shortcomings of the system, and thus bring about changes in folks’ behaviours.

– Bob

Further Reading

Marshall, R.W. (2021). All Agilists Are Unethical. [online] Think Different. Available at: /2021/12/23/all-agilists-are-unethical/ [Accessed 30 May 2022].
Seddon, J. (2015). 95% of Performance Is Governed By The System. [online] Vanguard Consulting Ltd. Available at: https://beyondcommandandcontrol.com/library/dr-demings-aphorisms/95-of-performance-is-governed-by-the-system/ [Accessed 30 May 2022].

We Need Your Help!

We so need your help in increasing the reach of our message about Quintessence. The more folks that get to hear, the sooner we’ll all benefit from a saner, more humane, more joyful way of delivering software. It’s way past time we all explored together what’s next.

We’re not asking you to subscribe to our assumption and beliefs. Just to mention (not recommend, not talk up) Quintessence to your friends, peers, colleagues and higher-ups.

Something along the lines of:

Have you heard about Quintessence? That batshit crazy Bob Marshall (FlowChainSensei) has invented/discovered an approach to software delivery entirely different from what we all know. He says it’s five times more productive than e.g. Agile approaches. Mental!

Would you be willing to help us spread the word about Quintessence.?

Thanks!

– Bob & Ian

Further Reading

Marshall, R.W. (2021). Quintessence: An Acme for Software Development Organisations. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/quintessence/[Accessed 25 May 2022].
Marshall, R.W. (2021). Memeology: Surfacing And Reflecting On The Organisation’s Collective Assumptions And Beliefs. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/memeology/ [Accessed 25 May 2022].
Marshall, R.W. (2018). Hearts over Diamonds: Serving Business and Society Through Organisational Psychotherapy. [online] leanpub.comFalling Blossoms (LeanPub). Available at: https://leanpub.com/heartsovediamonds/ [Accessed 25 May 2022].

The #NoSoftware Option

One of the many things that distinguishes The Quintessential Group from the Software Delivery also-rans is that our Quintessential Teams service provides our clients and prospective clients with a #NoSoftware option. John Seddon and his company, Vanguard Consulting, advise deferring software automation of new business processes and process steps at least until those steps have been trialed and proven through manual implementations – Post-its, paper-based processes, manual steps, etc. For those organisations that buy into this perspective, our #NoSoftware option means our teams will deliver these non-software solutions quickly and cheaply.

Also known as “software last”, a #NoSoftware solution is one that minimises the amount of software in a solution – in particular minimising the amount of custom-written software – ideally to the exclusion of software from the solution entirely.

As Steve Jobs famously said:

The way you get programmer productivity is not by increasing the lines of code per programmer per day. That doesn’t work. The way you get programmer productivity is by eliminating lines of code you have to write. The line of code that’s the fastest to write, that never breaks, that doesn’t need maintenance, is the line you never had to write.

~ Steve Jobs

The Benefits of #NoSoftware

  • Less maintenance overhead

The fewer lines of code in any given solution, the less needs to be spent on keeping that code up to date in line with e.g. changing requirements and discovered defects.

  • More flexibility

Did you know that the term “software” was first coined back in the 1950’s to reflect the idea that software could be changed more easily, quickly and at lower cost than the hardware solutions that then predominated? It was supposedly easier to change a line of code than to reroute traces on a PCB, or swap out soldered components. Nice wishful thinking, but it hasn’t turned out that way. Software is notoriously expensive, inflexible and difficult to change. Less software means increased flexibility and business agility.

  • Savings on up-front costs

Software costs money to write, even before it goes into service. Not only to pay for ever more expensive programmers and their friends, but also the opportunity costs of having to wait for the software to be ready to deploy. In most organisations this can mean months or even years of waiting.

  • Minimal automation

When a new business process or process step is implemented, it’s rare for the implementors to fully understand what’s needed, and to anticipated the unintended consequences of their choices. Premature automation can lock in inappropriate or suboptimal design choices. Once a process or process step has been up and running live in a manual form for some time, it’s generally easier to see where (limited) application of software-enabled automation may bring benefits. Hence “software last”.

  • Try before you buy

Use a #NoSoftware solution live in your business to prove your process or process steps to trial the solution before committing to implementing a software-based solution. You may actually find that a software-based solution is in fact unnecessary, or can be much more limited in scope – and cost – than originally imagined.

Attending To Folks’ Needs

Implicit in the idea of #NoSoftware is the imperative of attending to folks’ needs – the primary focus of The Quintessential Group. Generally speaking, folks have little need for software per se. As the old adage goes; folks don’t need a 1/4″ drill so much as they need a 1/4″ hole. When considering the means for attending to – and meeting – folks’ needs, software is often the default, but rarely the optimal means.

Chat More?

We’d be delighted to discuss the idea of our #NoSoftware solution option and how it will be suitable for your business or organisation. Curious? Please get in touch.

– Bob

Further Reading

Seddon, J. (2019). Beyond Command And Control. Vanguard Consulting.

There is helpful and useful content out there. But finding it amongst all the dross is a massive challenge.

I despair of the boatloads of naive advice, misinformation, and just pure tosh that so-called “Agile” people spout on a daily basis. (Not limited to just “Agile” people, of course.)

Caveat lector!

And just in case you’d like a sanity check on anything suspect or dubious, I’m always happy to support your natural scepticism. Just get in touch for non-partisan help.

Software Delivery Today

Software delivery today is in a state of crisis, and has been for decades. There is little recognition that available approaches are inadequate for meeting the needs of businesses of all stripes.

Of course, available approaches are seen as sufficient. But they do not deal adequately with the challenges we face in the day-to-day work of delivering solutions that meet folks’ needs. And in particular the need for predictability, flexibility and economy. We become swamped by the complexity of large solutions, lost in a maze of folks’ needs, and mystified by confusing and ambiguous priorities.

When we look at the typical mix of deployed solutions assembled from multiple sources, the situation is even worse.

The crisis in software delivery is far greater in overall magnitude at least than the situation of the early noughties. A situation that led to the spread of Agile approaches to relieve the burden of long timescales, delivering the wrong things, and highly risky schedules. The challenges are harder to solve and the costs of not solving them are in the $trillions. “The symptoms appear in the form of disengaged and demotivated employees, disgruntled and disappointed customers, unreliable, excessively expensive, untimely, inflexible and ultimately unsuitable solutions.”

There are ways to improve things a little, are they are slowly gaining recognition. But to achieve a fundamental jump in our delivery capabilities, we need to rethink what we doing, from first principles, and using a different frame.

– Bob

Further Reading

Firment, D. (2017). Tear Down The Wall Of Confusion. [online] Medium. Available at: https://cloudrumblings.io/devops-tear-down-the-wall-46656151d71d [Accessed 23 May 2022].

Celebrate With Us And Receive A Free Copy Of Quintessence!

To celebrate the launch of The Quintessential Group, our new software delivery startup, we’re making copies of my most recent book “Quintessence” – free for just one week <- coupon link. A $35.99 value! (And worth many more $$$ when applied).

If you’ve been curious about what’s the next big thing in the world of CKW (collaborative knowledge work) in general, and Software Delivery in particular, it’s all mapped out in detail in Quintessence. 

Whether you’re a developer looking for revolutionary ways of working (we choose rather to call it playing – and we’re inviting applications) or a business person looking to solve the software delivery crisis in your own organisation, there are many awesome things in the book for you.

Tell your friends, peers, teammates, co-workers and higher-ups. This is likely a one-time special offer!

– Bob

PS. I’ve just published a new version of the book (v1.5 – minor corrections and updates).

Want to get ahead of your competetion? Want to get in on the ground floor of the predominant approach to software delivery in the next twenty years (and more)? Simply read my latest book “Quintessence“. Those who’ve already read it say they love it to bits. 🙂

Or read the whole series, and get a deep understanding of the role of Organisational Psychotherapy in businesses of the future.

Further Reading

Marshall, R.W. (2021). Quintessence: An Acme for Software Development Organisations. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/quintessence/ [Accessed 20 May 2022].
Marshall, R.W. (2021). Memeology: Surfacing And Reflecting On The Organisation’s Collective Assumptions And Beliefs. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/memeology/ [Accessed 20 May 2022].
Marshall, R.W. (2018). Hearts over Diamonds: Serving Business and Society Through Organisational Psychotherapy. [online] leanpub.comFalling Blossoms (LeanPub). Available at: https://leanpub.com/heartsovediamonds/ [Accessed 20 May 2022].

An Exec’s Guide To Achieving Mission-critical Software Delivery

Nowadays, every business is a software business. Your enterprise needs to prioritise software delivery, be that deploying off-the-shelf solutions, commissioning bespoke software development, or a mixture of both.

Digital transformation: The term has been bandied about since it was coined more than a decade ago. I think we can all agree, though, that the “use of technology to radically improve performance or reach of enterprises” really gained momentum when the COVID-19 pandemic set in.

As we remember all too well, the entire world went digital within a matter of weeks, and companies raced to fulfil the soaring consumer demand for digital products and services. In fact, according to McKinsey, global businesses accelerated the adoption of digital offerings by an average rate of seven years — in a matter of just seven months. Some companies describe how they had to enable tens of thousands of home workers in just a few days!

The same McKinsey report shows that most business leaders see society’s digital shift as permanent. JPMorgan Chase’s CEO certainly thinks the increased use of digital apps and services is here to stay. He recently announced a 26% increase to Chase’s technology budget, focusing the $12 billion investment on further growing Chase’s portfolio of digital apps and services.

Providing innovative technologies is just half the job, though. There’s a lurking problem for business leaders: They can’t afford to let the delivery and integration of software into their businesses suffer delays and poor quality.

Just one schedule slippage in a key system can cause a cascade of problems. And when one of these slippages delays the deployment or upgrade of a key app or service, companies risk disrupted revenue streams, disgruntled customers, interrupted supply chains, lost productivity and frustrated staff.

Maintaining flow of software into the business is imperative to business continuity, but ensuring a steady, reliable flow is difficult. As businesses digitally transform and move their key processes to the cloud, and consumers utilise more digital innovations, their software estate grows in scale, complexity and fragility.

Consequently, maintaining the necessary software quality and delivery schedules must be a primary business objective. While leaders traditionally farmed out these responsibilities solely to their IT departments, technology has become so critical to business success that quality and delivery schedules can no longer hide in the opaque IT silo. It must – and has – become a culture and leadership issue.

Here are five steps executives can take to start embracing software quality, predictable schedules and steady flow:

Elevate Quality To Priority #1

When considering an enterprise’s numerous priorities, executives should take stock of the critical importance of quality. Does the company employ a virtual or hybrid workforce? Does the company interact or transact with customers online? Is revenue generated from online transactions? The questions can continue based on your industry, but chances are that most modern enterprises would agree they rely on a suite of software apps and software-based services for desired business outcomes.

Given the critical nature of digital apps and services — and their ability to provide a seamless experience for customers — executives should consider creating a culture of quality as a key performance indicator. Practically speaking, executives can and should treat quality numbers similarly to sales figures or other revered business metrics. One senior leader should be held accountable to the quality metrics and deemed responsible for relentlessly scrutinising and reporting on these figures alongside the business’s other KPIs.

If executives really want to underscore the importance of quality, they can walk the talk for their workforces. Business leaders can make quality a compensation-affecting business objective, like profit or sales targets. And they can tie these quality metrics back to the bottom line.

Focus On The People

In the era of “every business is a software business,” enterprises can no longer tuck away tech talent out of sight, removed from customer interaction. In fact, they should do the exact opposite, moving software folks to the front line and making them part of the business’s core value proposition. Actively marketing a company’s tech and nerd credentials will drive confidence in the brand’s digital presence. And enhance employer branding at the same time.

Naturally, redeploying the software folks goes both ways. Executives must also show genuine trust and respect for these key people. Even without extensive technical knowledge, business leaders can provide the kind of environment, and culture, that makes teams’ lives easier by reducing the cognitive load imposed by traditional management approaches. And they can give them the freedom to use modern paradigms like DevOps and CI/CD pipelines. Software teams with respect, resources and support will have a foot up on delivering innovations and protecting the quality of their deliveries.

Treat Unceasing Innovation As Standard

As most executives know, today’s world of digital business demands continuous innovation as a minimum requirement for keeping pace with competitors. This unceasing innovation requires executives to drop risk-averse postures and embrace reinvention and the concomitant continuous change.

Of course, amidst digital innovation, reinvention and even failure, quality remains a top priority. Executives need a business culture that allows their organisation to experiment, and sometimes falter, with the least amount of negative impact. After all, stagnation is no longer an attractive option.

Open The Chequebook and Invest!

If an enterprise relies on various digital apps and services for business performance, executives should guarantee the entire software delivery pipeline is exemplary.

While only the lucky few have an extra $12 billion on hand to invest in software delivery and the associated spend, executives should advocate for a big piece of the pie to go toward technology investment. And technology investment shouldn’t stop at commissioning delivery projects. Forward-thinking enterprises invest in next-generation delivery methods like Quintessence, alongside talent, training and time to innovate.

Make Technical Know-how A Leadership Must-Have

Executives should ask themselves a simple question: does anyone on the most senior team have “SDLC” or software delivery experience in their past or even present core competencies? While leadership teams are usually stacked with impressive qualifications — CPAs, MBAs and JDs — few include software people with practical SDLC experience. But given the importance of technology, executives should surround themselves with true technology practitioners.

A chief digital officer (CDO) can become a business leader’s quality czar. With a depth of SDLC experience, this role can help executives understand and benchmark their companies’ digital performance and balance digital transformation efforts with operations management.

Following these steps sends a clear message both internally and externally: innovating is no longer enough — changing the culture to remove the shackles of outmoded assumptions and beliefs is also necessary. If executives want to maximize their digital investments and thrive in a digital-first world, they must embrace quality and the culture that enables it.

– Bob