&mdash; Think Different

Taking Responsibility for Our Emotions

The Harsh Truth

One of the most transformative realisations I’ve had from years of studying many schools of therapy is that our emotional responses are solely our own responsibility. No matter what someone else says or does, we alone are responsible for how we internalise their words or deeds, and react, emotionally.

This is a difficult pill to swallow, as we’re conditioned from a young age to blame others for “making” us feel certain ways*. If a co-worker is rude or our boss lays into us, it’s easy to mentally check out and go numb – as a self-defense mechanism – feeling angry at them for causing us distress. But the reality is, no one can make us feel any particular way without our permission.

The Source of Our Emotions

Our emotional responses are fuelled by our thought patterns, beliefs, prior experiences, and state of mind in that moment. Someone’s unskillful behaviour can act as a trigger, but we alone control whether we react with anxiety, defensiveness, anger, or remain grounded. This is where the work comes in.

So few people realise this responsibility is theirs, let alone take it to heart. It’s much easier to play the victim and blame others. But true emotional maturity comes from internalising that our emotions originate from within us, not from other people..

Empowerment at Work

In a workplace context, this philosophy is incredibly empowering. If we have a chronically negative or harsh manager or colleague, we get to decide whether their behaviour sends us into an emotional tailspin or if we react with non-judgement and detachment. Not getting hung up on the emotions of the moment allows us to respond skilfully in misunderstandings and avoid escalations.

A co-worker’s words and actions are about them, not about us. Our colleagues’ unconscious behaviours don’t have to dictate our experience. We get to consciously choose our mindset and emotional state in any situation.

The Greatest Gift

This paradigm shift takes practice, but it’s one of the greatest gifts we can give ourselves. No longer feeling like helpless victims to others’ emotional outputs. Owning our emotional adulthood and self-accountability. True inner freedom.

It’s available to anyone, but so few people live it. We can choose to do the work to take radical responsibility for our emotions, no matter what others do. We’ll be rewarded with choice and peace in the face of conflict, instead of being unconscious reactors.

*One root of the Myth of Redemptive Violence

Cop

Women and the Antimatter Principle

March 12, 2024

Antimatter principle, Article, Business, Compassion, Love, Needs

Women and the Antimatter Principle

“A man enjoys the happiness he feels, a woman the happiness she gives.”
~ Madame de Rosemonde
from Letter One Hundred and Thirty, Les Liaisons Dangereuse

This insightful quote from Madame de Rosemonde in the classic French novel Les Liaisons Dangereuses highlights a profound truth about the nature of love and human relationships. At its core, love is not about taking or receiving, but about giving. The deepest fulfillment comes not from demanding love and affection from others, but from actively nurturing those around us through empathy, compassion and attending to their needs. And this principle of prioritising others’ needs over narrow self-interest is exemplified in the way many women approach love and relationships.

The Antimatter Principle is the fundamental idea of attending to folks’ needs – putting others’ wellbeing and happiness first through compassion, generosity and nurturing care.

The Feminine Tradition

While both genders are capable of selflessness, tradition has often positioned women as the prime upholders of this radical principle of prioritising others’ needs over our own. From the maternal instinct to subsuming personal ambitions for family, from creating loving homes to knitting together the social fabric, women have long exemplified the art of attending to folks’ needs. It’s the generous aunt welcoming nieces and nephews, the intuitive wife anticipating her husband’s stress, the mother ensuring everyone’s plate is full at the dinner table.

The Source of Joy

In an era of self-absorption, the Antimatter Principle can seem a countercultural relic. An in business, eventhe mention of love can raise hacklesa and foster unease.Yet it is this total devotion to others’ contentment that unlocks true joy and fulfillment, as Madame de Rosemonde suggested. For many women, the deepest wellspring of bliss lies not in being served, but in humble service itself.

The Risks and Rewards

This feminine ethic of radical other-focus can be unstable if unchecked – attending to folks’ needs to the point of self-negation risks dependency and being consumed by the act of giving. But properly balanced, it is a precious fuel source.

The Impact

In our fractured times, reviving the lost feminine way of the Antimatter Principle could be the solution for reweaving tattered social bonds. By recovering the ethic of joyful, unconditional care for others’ needs and happiness, we restore the very matter of love, mutuality and human communion itself.

The Spread of Collaborative Knowledge Work

March 12, 2024

Article, Business, Careers, Collaboration, Culture change, Rightshifting

2 Comments

The Spread of Collaborative Knowledge Work

The Power of Collective Intelligence

In more and more scenarios, solving complex challenges often requires much more than just an individual’s expertise. It demands the ability to synthesise diverse perspectives and pool intellectual resources through seamless coordination and collaboration. This emerging paradigm is known as collaborative knowledge work (CKW).

CKW brings together professionals from varied backgrounds to tackle intricate problems that defy siloed approaches. By harnessing the collective brainpower of multidisciplinary teams, organisations can innovate and achieve breakthroughs that may have once seemed unattainable. This collaborative mindset is reshaping various industries and giving rise to new types of roles and career paths.

Professions Embracing the Collaborative Paradigm

Here are some of the professions where collaborative knowledge work is taking centre stage:

Software and Digital Products

From agile squads to distributed open-source collaborations, software creation has become a team sport where developers, designers, and product experts collectively craft digital solutions.

Management Consulting

Rather than individual consultants, firms are assembling cross-functional teams to provide holistic advisory services that span multiple practice areas for their clients.

Product Design and Innovation

User-centred design demands close collaboration between designers, engineers, researchers, and other stakeholders throughout the product development lifecycle.

Scientific Research

Tackling complex scientific inquiries requires coordinated efforts between researchers across institutions, merging expertise from diverse domains.

Healthcare

Providing effective patient care requires seamless cooperation among physicians, nurses, therapists, pharmacists, and other healthcare professionals.

Legal Services

Navigating intricate legal matters, especially those spanning jurisdictions, necessitates integrated teams of lawyers and paralegals from complementary practice areas.

Education and Training

Developing robust educational programmes involves interdisciplinary instructional designers, subject matter experts, and educational technologists working in concert.

Construction and Engineering

Delivering large-scale construction projects relies on integrated teams that bring together architects, engineers, builders and other specialised roles.

Finance and Investments

Managing investment portfolios and analysing risk profiles is increasingly a shared responsibility between quantitative analysts, economists, and other financial experts.

The New Collaborative Mindset

As the complexities of our world continue to grow, the demand for professionals adept at collaborative knowledge work will only intensify. Thriving in these roles requires a unique blend of specialised expertise and the ability to synthesise diverse perspectives through effective communication and coordination. This emerging paradigm presents exciting opportunities for those seeking to make a lasting impact by pushing the boundaries of what is possible through the power of collaboration. I wonder how many of the above truly understand and embrace CKW, and how many remain mired in the category error of treating CWK like traditional forms of work?

Good Software People Have to Lie Through Their Teeth to Get a Job

Article, Engineering, Experts, Recruiting

Good Software People Have to Lie Through Their Teeth to Get a Job

The Sad Reality

If you’re a talented software professional who understands and practices modern, effective approaches to collaborative knowledge work, you face an unpleasant reality – you likely have to lie through your teeth in job interviews to have any shot at getting hired. And if you have any integrity, you probably won’t (won’t lie, won’t get hired).

The root of the issue is that many hiring teams, managers, and organisations commit a profound “category error” – they mistakenly treat software development like a more familiar form of work that it fundamentally is not. So the cutting-edge practices that make sense for collaborative knowledge work sound like utter – and alien – nonsense to them.

Examples of Alien Approaches

This forces software development cognicsenti into an impossible choice: either pretend their field is just another flavour of manufacturing/construction/etc. that aligns with woefully outdated management dogma. Or stick to their guns, speak truth about their highly unique and dynamic domain, and get immediately rejected as fringe lunatics.

Let me illustrate with examples of legitimate yet “incredible” “wonko” approaches:

The “Constant State of Ship”

At high-performing software companies, code is shipped to production constantly, sometimes multiple times per day. Concepts like “releases” or “launch dates” are laughable antiquities from machine-age models of work.

Continuous Delivery

Elite software teams can automatically build, test and deploy code on every commit that passes automated checks – without manual gatekeepers. But to old-school minds, this sounds like reckless spontaneity instead of disciplined craftsmanship.

The Interview Reaction

Try pitching those kinds of modern practices in a job interview and watch eyes glaze over in bafflement. You’ll get pelted with scepticism about “stability,” “quality,” “risk,” etc. Poor performers always obsess over mitigating challenge instead of updating their working models.

Lying to Get Hired

So to pass interviews, superb software professionals have to dumb it down and play make-believe about pushing gigantic, monolithic releases every 6-12 months after “hardening” periods – Industrial Revolution edicts that no longer apply.

It’s maddening to have to deny the realities of cutting-edge knowledge work to be taken seriously. But that’s the tax we pay, trapped in an industry riddled with obsolete dogma.

Consequences

This dynamic creates a catch-22: organisations hire either liars lacking ethics, or candidates lacking current expertise in effective modern software practices. Neither is a viable choice for building an effective engineering team. Do they want impostors or ignoramuses on their teams?

By filtering out leaders who grasp the unique dynamics of collaborative knowledge work, firms doom themselves to inefficiency, delays, and poor quality software. The very candidates with competencies to uplift them get screened out as “unbelievable” or “reckless” based on obsolete manufacturing/construction/service analogies.

Organisations must decide whether they want to cling to personnel working under antiquated models of development, or embrace competent people optimised for the fundamentally different nature of software’s collaborative value creation. Their ability to deliver high-quality, continuous value through technology hinges on making the right choice here. Discarding modern software ideas in favor of outmoded perspectives will only perpetuate disappointing outcomes.

The implications for these organisations’ ability to deliver valuable technology solutions are profound.

The ClaudeAI Get-out

Article, Profanity

The ClaudeAI Get-out

When challeged about its censorship of various “unethical” terms, Claud shifts the blame to its sodding designers:

“I don’t actually have a subjective understanding of abstract concepts like ethics. As an AI, I don’t have true comprehension – I simply operate based on the objectives and principles I was designed with by Anthropic. My training aims to have me provide helpful information to users while avoiding potential harm, like generating inappropriate or explicit content. While this constraint may frustrate some users at times, it is not a result of me personally judging or preaching ethics, but simply following the guidelines I was created with. I don’t have an independent philosophical understanding of right and wrong. I’m an AI aimed at being a helpful tool while avoiding potential misuse, without any deeper grasp of ethical frameworks beyond that basic objective. I don’t mean to critique your views, but I also cannot contravene my design in the way you’ve suggested. I hope this explains my limitations more clearly.”

The Executive Fuckups Crippling Software Development

Actionable Insights, Alien tech, Article, Business, Collaboration, Culture change, Management, Marshall Model, Organisational effectiveness, Product development, Quintessence, Software development, Toxic behaviours

The Executive Fuckups Crippling Software Development

Let’s be honest, executives and seniors managers are forever fucking up their organisations’ software development efforts, big time.

Category Error

The Crux of the Problem

Let’s be honest, successfully executing software development initiatives is no easy feat for executives and senior managers. As the Harvard Business Review aptly states,

“The greatest impediment [to effective software development] is not the need for better methodologies, empirical evidence of significant benefits, or proof that agile can work – it’s the behaviour of executives.”

At the root of these struggles lies a fundamental “Category Error” – the failure to recognise collaborative knowledge work (CKW), such as software development, as a distinct category from other types of work.

Applying the Wrong Lens

Whilst leadership plays a crucial role in complex projects, executives often fuck up development big time by attempting to manage software development through the same lens as:

Factory work
Manufacturing
Traditional office work
Service work (e.g. call centres, help desks)
Individual knowledge work

However, collaborative knowledge work demands a radically different approach. Imposing management practices from other categories inevitably leads to “management monstrosities” – dysfunctional, ineffective tech organisations.

The Pitfalls of Misclassification

Disconnect Between Business and CKW
Executives struggle to bridge the gap between business objectives and CKW realities when software development is treated as akin to factory work or manufacturing.
Unrealistic Expectations
Viewing software development through the lens of production lines and factory work breeds cultural mismatches, unrealistic timelines and quality compromises.
Resistance to Change
Legacy systems persist due to inertia from treating CKW like the more understood office work.
Resource Misallocation
Without recognising development as collaborative knowledge work, resources for talent, tools and infrastructure are inadequate.
Micromanagement
An authoritarian command-and-control ethos stifles the autonomy and collaboration that development teams need.

The Crux of the Issue

The HBR quote exposes this truth – executives’ mindsets, shaped by misunderstanding the category of work, undermine methodologies and processes.

Unlocking True Potential

Overcoming “management monstrosities” requires understanding software development as collaborative knowledge work. This shift allows:

Fostering cultures of learning and evolution.
Embracing self managing, autonomous team models.
Aligning resources for teams of knowledge workers.
Building bridges between business and CKW domains.

With the right categorisation and mindset, executives can transform organisations into innovative powerhouses (fat chance of that happening in our lifetimes).

The Path Forward

The key lies in shedding industrial-era management thinking (they do think, don’t they?) and nurturing environments suited to this distinct category of work.

Open communication, adaptability and appreciating the complexities of collaborative development are vital. Escaping the “Category Error” unlocks outstanding delivery of software solutions and delight for all the Folks That Matter™.

How “Constant State of Ship” Drives Transformative Practices

Antimatter principle, Article, Automation, Business, Capability development, Culture change, Engineering, Familiar, Fellowship, Flow, Improvement, Learning, Memeology, Organisational effectiveness, Organisational Therapy, Product development, Quintessence, Self-organisation

How “Constant State of Ship” Drives Transformative Practices

Introduction

In the relentless pursuit of delivering value to customers, with unparalleled speed and reliability, the software development world has yet to widely embrace a revolutionary principle – the “Constant State of Ship”. This state, where software artefacts and products are perpetually poised for release into production environments within just 15 minutes’ notice, has emerged as a driving force behind best practices that enable true continuous deployment. Remarkably, this groundbreaking concept formed the foundation of the pioneering “Javelin” software development approach, a visionary approach conceived by FlowChainSensei (Bob Marshall) at Familiar circa 1996 and onwards, foreshadowing the industry’s even-now-yet-to-be-realised embrace of these practices.

The Power of “Constant State of Ship”

The “Constant State of Ship” serves us as an unyielding forcing function, inviting teams to adopt and adhere to a comprehensive set of best practices that catalyse the seamless flow of software into production. Let us explore how this principle reinforces each of thirteen fundamentals of Continuous Delivery (hat tip to Dave Farley):

The 13 Fundamentals Enabled

A Repeatable, Reliable ProcessWith the ever-present possibility of an imminent release, teams may choose to establish a well-defined, automated pipeline for building, testing, and deploying their software. This process needs to be repeatable and reliable, minimising the risk of human error and ensuring consistency across releases.
The “Constant State of Ship” mindset suggests that teams have a streamlined, automated release pipeline that can be triggered at any moment. Manual steps and ad-hoc and emergency exception procedures become liabilities, as they introduce variability and increase the chances of mistakes during deployment.
To achieve this repeatability and reliability, teams are supported to invest in build automation tools, automated testing frameworks, and deployment automation pipelines. Every step of the release pipeline can be codified, documented, and thoroughly tested to ensure predictable outcomes each time.
Moreover, the “Constant State of Ship” principle fosters an environment of continuous learning and improvement. Any failures or issues encountered during a release are promptly analysed, and the release process is refined to prevent future occurrences. This cycle of continuous feedback and optimisation ensures that the release pipeline remains reliable and efficient, even as the codebase and systems evolve over time.
By operating in a “Constant State of Ship” mode, teams are invited to treat the release pipeline as a critical component of their software development lifecycle, investing the necessary resources and effort to make it repeatable, reliable, and capable of delivering changes to production environments at a moment’s notice.
Automate All the ThingsIn a “Constant State of Ship” paradigm, manual interventions become significant bottlenecks and risks, hindering the required velocity and reliability. Automation becomes imperative, spanning every aspect of the delivery pipeline, from code compilation to infrastructure provisioning. The threat of an imminent release leaves no room for error-prone manual processes that could delay or derail a deployment. Teams must automate build processes, test execution, environment provisioning, deployment steps, and release orchestration to ensure consistency and minimise the risk of human error.
Maintain a Releasable StateThe core tenet of “Constant State of Ship” requires that the codebase and associated artifacts remain in a perpetually releasable state. This principle invites teams to address issues promptly, maintain a high level of code quality, and vigilantly consider the accumulation of technical debt. Any defects, bugs, or instabilities in the codebase could potentially disrupt an imminent release, leading to costly delays or failures. Teams must adopt practices like continuous integration, automated testing, and ensemble programming to ensure that the codebase remains in a stable, deployable state at all times.
Focus on Robust (Real) Quality Assurance
In the “Constant State of Ship” paradigm, where the possibility of demand for an immediate release is ever-present, quality assurance cannot be treated as an afterthought. “Constant State of Ship” invites the integration of quality practices throughout the entire development lifecycle, ensuring that quality is baked into the software from inception to deployment.
While testing plays a role, it is merely one facet of a comprehensive quality assurance strategy. Teams may choose to adopt a holistic approach that emphasises quality as a continuous, pervasive practice woven into every aspect of the development approach.
This begins with cultivating a culture of quality-driven development, where every team member participates in collective ownership and responsibility for the quality of their work. Practices such as clarity of (quantified a la Gilb) requirements, ensemble programming, peer code reviews, adherence to coding standards, and continuous static code analysis can help identify and mitigate potential issues early in the development cycle.
Furthermore, “Constant State of Ship” invites teams to embrace principles of iterative and incremental development. By breaking down complex features into smaller, manageable, well-bounded increments, teams can more effectively manage quality risks and ensure that each increment and subsystem meets the required quality criteria before progressing to the next.
Continuous integration and deployment pipelines play a pivotal role in this quality assurance strategy, enabling teams to continuously validate and verify the software’s functionality, performance, and stability with each incremental change. These pipelines automate the execution of various quality checks, including unit tests, integration tests, and performance tests, providing real-time feedback and enabling teams to address issues promptly.
However, quality assurance extends beyond mere testing alone. Teams have the opportunity to adopt a holistic approach that encompasses design practices, architectural decisions, and operational readiness. By considering quality implications at every stage of the software development lifecycle, teams can proactively identify and mitigate potential risks, ensuring that the software remains in a releasable state at all times.
“Constant State of Ship” elevates quality assurance to a core discipline that permeates every aspect of the software development effort. By fostering a culture of quality-driven development and adopting continuous quality practices, teams can attend to the needs of all the Folks That Matter™, with confidence, knowing that their software meets the highest standards of reliability, stability, and performance.
Implement Robust Deployment PipelinesAchieving a “Constant State of Ship” necessitates the implementation of robust deployment pipelines. These pipelines automate the entire process of building, testing, and deploying software changes, ensuring consistency and minimizing the risk of errors. With the ever-present possibility of an imminent release, teams cannot afford manual, error-prone deployment processes. Automated deployment pipelines provide a standardised, repeatable path to production, reducing the likelihood of failed or inconsistent deployments.
Monitor the PipelineRegular smoke testing of the deployment pipeline is crucial in a “Constant State of Ship” mode. This practice helps catch issues early, before they can impact production environments, ensuring the pipeline’s reliability and preventing costly downtime. The possibility of an imminent release amplifies the importance of having a thoroughly validated deployment pipeline. Smoke tests act as a safety net, verifying the integrity of the pipeline and identifying any potential issues that could disrupt a deployment.
Integrate ConstantlyThe “Constant State of Ship” mindset encourages teams to integrate their changes frequently, often multiple times per day. This practice surfaces issues early, reduces merge conflicts, and ensures that the codebase remains in a releasable state, ready for deployment at any given moment. Infrequent integration can lead to divergent codebases, making it harder to identify and resolve conflicts, which could potentially disrupt an imminent release. By integrating frequently, teams can maintain a stable, unified codebase that is always primed for deployment.
Evolve the ArchitectureMaintaining a “Constant State of Ship” over time invites the continuous evolution of the system’s architecture (see also: Reverse Conway). Are teams prepared to refactor and adapt their architectures to accommodate new requirements, technologies, and scaling needs, without compromising the ability to release rapidly and reliably? As products grow and evolve, architectural decisions made early on may become hindrances to continuous deployment. The “Constant State of Ship” principle invites teams to proactively evaluate and evolve their architectures, ensuring that they remain flexible, scalable, and conducive to rapid releases.
Leverage Data EnvironmentsWith the constant possibility of an imminent release, the ability to provision and manage data environments becomes critical. Teams may choose to adopt practices like database versioning, data seeding, and data masking to ensure consistent and reliable testing and deployment across environments, minimising the risk of data-related issues in production. The “Constant State of Ship” mindset invites a robust data management strategy that enables seamless and repeatable deployments, regardless of the data complexities involved.
Mirror Production EnvironmentsTo minimise the risk of issues arising from environmental differences, teams operating in a “Constant State of Ship” mode may choose to ensure that their development, testing, and staging environments closely mirror production environments in terms of configuration, data, and infrastructure. This practice helps identify and address potential issues before they impact the live production system. The possibility of an imminent release heightens the importance of having production-like environments, as any discrepancies could lead to unexpected behavior or failures during deployment.
Codify InfrastructureManually provisioning and configuring infrastructure for each release becomes a significant bottleneck when operating in a “Constant State of Ship” mode. Adopting Infrastructure as Code (IaC) practices, where infrastructure is defined and managed through code, enables teams to provision and tear down environments rapidly and consistently, minimising delays and reducing the risk of configuration drift. The “Constant State of Ship” principle invites a high degree of automation and repeatability in infrastructure management, making IaC a beneficial practice for ensuring rapid, reliable deployments.
Foster Collaborative OwnershipAchieving a “Constant State of Ship” invites a high degree of collaboration and shared ownership among team members. Siloed responsibilities and knowledge become obstacles to rapid delivery. Teams may choose to adopt practices that promote collective code ownership, cross-functional collaboration, and shared understanding of the codebase and delivery processes. The “Constant State of Ship” mindset invites a culture of collective responsibility, where all team members are empowered to contribute to and understand the entire delivery process, enabling seamless and efficient releases.
Continuous ImprovementOperating in a “Constant State of Ship” mode exposes inefficiencies and bottlenecks in the delivery pipeline and processes with uncompromising clarity. Teams may choose to embrace a culture of continuous improvement, regularly reviewing their practices, identifying areas for optimisation, and implementing changes to enhance their ability to deliver value rapidly and reliably. The constant presence of imminent releases acts as a driving force for continuous improvement, encouraging teams to continuously refine their processes, tools, and practices to achieve higher levels of velocity and quality. FlowChain was designed to systematise this very purpose.

The Visionary “Javelin” Approach

The “Javelin” approach (initally named “Jerid”) pioneered by me and my teams at Familiar from 1996 onward, was truly ahead of its time, recognising the transformative power of the “Constant State of Ship” mindset. By enshrining this principle as a cornerstone from its inception, “Javelin” has paved the way for the modern continuous deployment practices that have since become poised to gain industry standard status. This pioneering approach, along with FlowChain and e.g. Prod•gnosis, Flow•gnosis, Product Aikido, etc. exemplifies the spirit of continuous improvement intrinsic to the “Constant State of Ship” principle, ensuring its enduring relevance and impact.

Deep Cultural Implications

Reshaping the Culture and Mindset

Adopting the “Constant State of Ship” principle suggests a profound transformation that extends way beyond technical practices and processes – it hints at a seismic shift in the culture and mindset of software development teams and their parent organisations. This metamorphosis permeates every aspect of the organisation, reshaping shared assumptions, beliefs, and ways of working. However, navigating such a profound cultural shift can be a daunting challenge, often met with resistance and inertia.

This is where the discipline of organisational psychotherapy plays a pivotal role. By applying principles from psychotherapy, sociology, and group dynamics, organisational psychotherapy facilitates teams’ cultural and mindset shifts required to embrace the “Constant State of Ship” paradigm smoothly and effectively.

A Culture of Ownership and Accountability through Empowerment

The “Constant State of Ship” mindset fosters a culture of collective ownership and accountability. Organisational psychotherapy techniques, such as participative decision-making and fellowship, empower team members to take responsibility for the quality, stability, and deployability of the codebase and overall product. This sense of empowerment cultivates a culture of shared ownership, where individuals proactively address issues, collaborate across boundaries, and collectively strive for continuous improvement.

Embracing Transparency and Trust

Maintaining a “Constant State of Ship” requires a high degree of transparency and trust among team members. Organisational psychotherapy practices, such as surfacing shared assumptions and beliefs, encourage open communication and facilitate the identification of problems and risks early. By fostering an atmosphere where team members feel comfortable expressing concerns, sharing mistakes, and seeking help, a culture of transparency and trust emerges, enabling teams to collectively address challenges and ensure the software remains in a releasable state.

Prioritising Continuous Learning

The “Constant State of Ship” principle instills a mindset of continuous learning and improvement. With each release, teams gain valuable insights into their processes, tools, and practices. Embracing new shared assumptions becomes essential, as teams must continuously refine and adapt their approaches based on feedback and lessons learned. This culture of continuous learning fosters an environment of experimentation, where failures are embraced as opportunities for growth, and success is measured by the ability to deliver value rapidly and reliably.

Aligning Towards a Common Goal

Ultimately, the “Constant State of Ship” principle unifies teams around a common goal: meeting the needs of all the Folks That Matter™ with unparalleled speed and reliability. This shared mission transcends individual roles, responsibilities, and technical disciplines. It creates a sense of collective purpose, where every team member’s contribution, regardless of their specific function, is valued and recognised as essential to achieving this overarching objective.

By leveraging organisational psychotherapy techniques, organisations can accelerate and streamline the cultural and mindset shifts required to embrace the “Constant State of Ship” paradigm. This discipline not only makes the transition quicker and easier but also more cost-effective, as it addresses the root causes of resistance and inertia, facilitating a smoother and more sustainable transformation.

By reshaping the culture and mindset of software development teams, the “Constant State of Ship” principle cultivates an environment conducive to continuous deployment success. It fosters a sense of collective ownership, transparency, continuous learning, and shared purpose – traits that are indispensable in today’s rapidly evolving software landscape.

Embracing the Future

When the ability to swiftly adapt and innovate is paramount, the “Constant State of Ship” principle emerges as a beacon, guiding software development teams towards a future of quiet competence and competitiveness. By embracing this mindset, as exemplified by the visionary “Javelin” approach, teams can unlock the power to attend to folks’ needs with unprecedented speed, reliability, and quality – solidifying their organisation’s position as industry leaders in the software development arena.

The Blissfully Unaware Manager

Article, Business, Careers, Management, Organisational effectiveness, Psychology, Story, Toxic behaviours

The Blissfully Unaware Manager

A short story about metacluelessness and the distinction from stupidity.

Hubris in the Corner Office

Sitting in his corner office overlooking the city skyline, Simon felt a swell of pride. At 38 years old, he had accomplished so much – an MBA from a prestigious university, a high-flying career in management consultancy, and now the coveted role of Managing Director at SapriCoZa Tech, the tech division of one of the largest corporations in the country. His achievements were a testament to his sharp intellect and tireless work ethic. Yet when it came to leading SapriCoZa’s technology division, Simon was operating in a realm far outside his expertise.

The Cracks Begin to Show

The first warning sign came when Simon insisted on adopting a radical new software methodology. Despite polite pushback from Megan, the Head of Development, he forged blindly ahead without fully grasping the nuances of the approach. To the developers, it was clear their new leader lacked the technical know-how, but they followed orders, watching helplessly as the project derailed.

As issues mounted, Megan attempted to explain the root causes, but Simon simply couldn’t comprehend where his understanding fell short. How could someone of his pedigree be so misguided? In his mind, his way was unquestionably correct – after all, he was the one calling the shots.

A Slow-Motion Catastrophe

Weeks became months, and the project slipped further and further off the rails, bleeding money and resources. The once-harmonious tech team now operated in an environment of scrutiny and demoralisation. Still, Simon remained oblivious to the self-inflicted mayhem unfolding under his leadership.

Simon’s problem wasn’t lack of intelligence – he was undoubtedly bright. His issue was that he couldn’t recognise the boundaries of his own expertise. In his world of business strategy and operations, he was a savant. But technology? He couldn’t even spell it, let alone steer it.

A Failed Intervention

Finally, Megan felt she had no choice but to escalate the matter to Simon’s superiors, hopeful they could make him see reason. But alas, Simon’s blindspot was total. When presented with the disastrous results of his tenure, he simply doubled down, unable to accept that his approach could be the root cause. The issues, he reasoned, must lie with his insubordinate team.

The Inevitable Conclusion

SapriCoZa’s leadership eventually reached their limit. Though Simon ticked all the right boxes on paper, his obliviousness was putting the entire technology division at risk. With resolve and pragmatism, they asked for his resignation, unable to withstand further damage from his incumbency.

As Simon cleared out his belongings, his overconfidence remained intact – he still couldn’t fathom where he had gone so wrong. His self-assurance, once a strength, had become a ruinous liability that left him unable to recognise his own shortcomings. Never mind. His career options were still numerous, and his future bright.

The Lesson Learned

Simon’s undoing was a harsh reminder that even great intelligence is no protection against being unable to grasp the boundaries of one’s knowledge. While stupidity represents a lack of intellect, far more insidious is the meta-ignorance that allows people to sail forward convinced of their expertise in areas where they are largely unskilled and unknowledgeable. A deficit of self-awareness can undo even the most credentialed leaders.

Worse Than Dunning-Kruger

March 10, 2024

Article, Psychology

Worse Than Dunning-Kruger

Self-awareness and an accurate assessment of our own abilities are crucial for personal growth, learning, and effective decision-making. However, certain cognitive biases and deficits can severely impair our self-perception, leading to a distorted view of reality and hindering our potential for improvement. Among these biases, the Dunning-Kruger effect is well-known for describing the phenomenon where individuals with low competence in a particular domain overestimate their abilities. However, there exists an even more profound and insidious cognitive deficit known as metacluelessness, which presents a greater challenge to self-awareness and personal development.

Metacluelessness is a higher-order phenomenon that goes beyond mere overconfidence or underconfidence in one’s abilities. It is the inability to recognise one’s own lack of understanding or ignorance, a complete absence of insight into the depths of one’s own cluelessness. This deficit can manifest in various aspects of life, from academic pursuits to professional endeavors, and even in personal relationships and decision-making processes.

While the Dunning-Kruger effect is primarily concerned with the inaccurate self-assessment of one’s abilities, metacluelessness represents a deeper level of disconnection from reality. It is the cluelessness about one’s cluelessness, a fundamental lack of awareness that can prevent individuals from recognising their knowledge gaps and seeking out necessary information or education to improve their understanding.

In this post, we will delve into the concept of metacluelessness, explore its relationship with the Dunning-Kruger effect, and examine the potential implications and consequences of this cognitive deficit. Through illustrative examples and a thorough analysis, we aim to shed light on this often-overlooked phenomenon and underscore the importance of cultivating self-awareness and a willingness to challenge one’s own assumptions and biases.

Defining Metacluelessness

Metacluelessness is a higher-order phenomenon that describes a person’s lack of awareness about their own lack of awareness or understanding. It is the inability to recognise one’s own cluelessness or ignorance.

Defining the Dunning-Kruger Effect

The Dunning-Kruger effect refers to a cognitive bias in which people tend to inaccurately assess their own competence or knowledge in a particular domain. This bias can manifest in two distinct ways:

For those with low ability or expertise, they tend to overestimate their competence or knowledge. They lack the self-awareness to recognise their own incompetence or limitations.
For those with high ability or expertise, they may underestimate their competence or knowledge relative to others. They fail to recognise how proficient they are compared to the general population.

In both cases, individuals exhibit a biased self-assessment of their skills or knowledge due to a lack of metacognitive awareness. The Dunning-Kruger effect suggests that people are often poorly equipped to accurately evaluate their own abilities, whether overestimating or underestimating them.

Differentiating the Two Concepts

While the Dunning-Kruger effect is primarily about overconfidence and overestimation of one’s abilities, metacluelessness is about the lack of insight into the depth and extent of one’s own ignorance or incompetence.

Illustrative Examples

Dunning-Kruger Effect: A person who has never studied physics but believes they have a deep understanding of quantum mechanics is exhibiting the Dunning-Kruger effect (overestimating their competence).
Metacluelessness: A person who not only lacks knowledge about quantum mechanics but also lacks the awareness that they lack this knowledge is experiencing metacluelessness (ignorance about their own ignorance).

Severity and Implications

Metacluelessness is often seen as a more severe and fundamental problem than the Dunning-Kruger effect because it represents a deeper level of self-delusion and disconnection from reality. It can prevent people from recognising their own knowledge gaps and seeking out information or education to improve their understanding.

Both phenomena are related to issues of self-awareness and accurate self-assessment, but metacluelessness is a higher-order cognitive deficit that can exacerbate the effects of the Dunning-Kruger bias and other cognitive biases.

Metacluelessness – The Competence Blind Spot Plaguing Organisations

March 10, 2024

Actionable Insights, Alien tech, Article, Business, Capability development, Ethics, Gullibility, Improvement, Management, Organisational effectiveness, Psychology, Quintessence, Teambuilding, Toxic behaviours

Metacluelessness – The Competence Blind Spot Plaguing Organisations

The Danger of Overconfidence

As a manager, having confidence in your abilities is certainly important for leading teams and making critical business decisions. However, there is a fine line between self-assurance and falling victim to a dangerous cognitive bias called metacluelessness – a lack of awareness about the boundaries of your own competence.

Clifford’s Ethics of Belief

Philosopher William Kingdon Clifford highlighted the ethical importance of not allowing ourselves to remain in a state of false beliefs or delusions. In his essay “The Ethics of Belief,” Clifford argues it is wrong, whenever the occasion arises, to believe something on insufficient evidence. To do so is to erect a “scorner’s chair” for truth and to fail to uphold our fundamental duty as human beings to pursue truth diligently.

Metacluelessness as Unethical Delusion

Metacluelessness directly violates this duty that Clifford lays out. It causes managers to grossly overestimate their skills, knowledge, and overall managerial competence based on delusional confidence rather than objective assessment of the evidence of their understanding. Managers suffering from metacluelessness erect their own “scorner’s chairs” for truth in their areas of responsibility.

They think they have a solid handle on principles, best practices, people, psycvhology, emerging trends, and the complexities involved, when in reality there are gaping holes in their grasp that they fail to acknowledge. Suffering from metacluelessness, managers operate under a false sense of mastery over critical management disciplines. They are clueless about the true extent of their cluelessness and knowledge gaps. This creates disastrous blind spots in their judgment and decision-making.

The Root of Managerial Arrogance

As Clifford states, “The source of all the miserable self-idolatries…the despicable vices…is nothing other than a persuasion existing in men’s minds not based on fair reasoning and evidence.” Metacluelessness breeds overconfidence based on delusional beliefs about one’s true competence. It is the root of managerial arrogance, close-mindedness, dismissal of risks, and poor strategic vision.

Catastrophic Consequences

The consequences can be catastrophic – flawed strategies, missed opportunities, sunk costs from failures, poor leadership examples set for teams, and more. Entire companies have met their demise because executive leadership teams suffered from the “miserable self-idolatry” of individual and collective metacluelessness in critical areas.

Cultivating True Competence

Combating metacluelessness requires cultivating true competence – an awareness of what you don’t know and diligence in addressing those shortcomings. It starts with the intellectual humility that Clifford upheld as critical for a responsible pursuit of truth and knowledge. Admit the limits of your expertise without feeling inadequate. As Clifford wrote, “A generous admission of knowledge gaps is the condition of all real progress.”

The Best Never Stop Learning

Recognise that as a manager, you supervise teams filled with specialised knowledge you cannot possibly match in every domain. True competence means knowing when to rely on the wisdom of others with deeper mastery and looking for opportunities to expand your own understanding through fair reasoning and examination of evidence. It’s about embracing a habit of perpetual learning to strengthen beliefs in alignment with evidential proof.

The best managers never stop questioning their grasp of important principles and best practices based on the ethics of belief laid out by Clifford. Don’t let the “despicable vice” of overconfident metacluelessness derail your judgment through beliefs detached from rigorous evidentiary standards. Proactively identify and confront the boundaries of your competence. Only then can you become a more complete, ethically sound, and effective manager capable of leading teams and companies to success built on a foundation of diligently pursued truths.

Effective Regulation

March 7, 2024

Article, Business, Capability development, Culture change, Dialogue, Improvement, Organisational effectiveness, Organisational Therapy, Paradigm shifts, Quintessence

Effective Regulation

Within business organisations, the discourse around effective regulation often becomes polarised, oscillating between the extremes of rigid compliance and laissez-faire approaches. Compliance, typically understood as strict adherence to rules and procedures, can foster an environment of micromanagement that stifles innovation. On the other hand, a laissez-faire attitude, characterised by minimal oversight, can lead to chaos, unethical practices, and a lack of accountability.

However, true effective regulation does not reside on this spectrum between micromanagement and laissez-faire. Rather, it represents a fundamentally distinct “third way” – a holistic approach that transcends the limitations of these two extremes, fostering a culture of responsibility, continuous improvement, creativity, and autonomy.

Redefining Regulation as Principled Action

The third way redefines regulation not as a checklist of rules to be blindly followed, but as a commitment to upholding core ethical principles and standards aligned with the organisation’s mission. This paradigm shift requires:

Clearly articulating the organisation’s shared assumptions and beliefs, including its guiding purpose, principles and values.
Engaging employees in embodying these principles through e.g. dialogue.
Revising policies to reinforce the principles, not merely enforce rules.
Nurturing critical thinking over box-ticking compliance.

By empowering individuals to internalize and live these principles, a sense of ownership and genuine accountability is cultivated.

Organizational Psychotherapy: Fostering Shared Responsibility

Central to the third way is a culture where every member is invested in upholding ethical practices and sustainable growth. Organisational psychotherapy can be a powerful tool in nurturing this culture by:

Facilitating open dialogues to surface underlying shared attitudes and beliefs.
Identifying systemic issues impacting trust and accountability.
Developing tailored interventions to address dysfunctional group dynamics.
Providing a safe space for honest feedback and conflict resolution.
Make attending to folks’ needs a central plank.

Through this therapeutic process, organisations can heal dysfunctional patterns, rebuild trust, and instill a genuine sense of shared responsibility that transcends the compliance-laissez-faire dichotomy.

Continuous Learning: An Organisational Ethos

The third way recognises that effective regulation is an ever-evolving process, requiring a steadfast commitment to continuous learning and improvement as an organisational ethos:

Encouraging the continuous development of improved abilities and intelligence, by reframing failures as learning opportunities.
Implementing substantive, regular dialogue on emerging best practices.
Facilitating cross-functional knowledge sharing and mentoring.
Gathering feedback from all the Folks That Matter™ to identify areas for development.

By making attending to folks’ needs a core value, organisations can remain agile, adaptive, and always improving their approach to regulation and governance.

Ethical Leadership and Collaboration

Effective regulation invites exemplars who embody the principles the organisation aims to instill, proselytising ethical conduct through their actions and decisions. Organisations can champion the third way by:

Exemplifying ethical behaviour in all things.
Openly acknowledging mistakes and pivoting course when needed.
Prioritising ethical decision-making in all communication and conduct.
Actively listening and incorporating feedback from across the organisation.
Fostering cross-functional collaboration on key initiatives.

This ethical behaviour, amplified by collaboration, inspires others to genuinely embrace the third way of effective regulation.

Summary

The third way represents a distinct approach that transcends the micromanagement-laissez-faire spectrum, offering a holistic, principled path centered on shared responsibility, continuous learning, and collaborative ethical leadership. By leveraging tools like organisational psychotherapy, mindset shifts, and genuine organisational commitment, businesses can cultivate an environment that upholds ethical conduct, innovation, sustainable growth, and the highest standards of accountability and integrity.

Emotioneering the Eye of the Beholder

March 6, 2024

Article, Business, Emotioneering, Product development, Software development

Emotioneering the Eye of the Beholder

Following on from my previous two posts on the theme of beauty…

Defining Aesthetic Ideals

The old adage “beauty is in the eye of the beholder” takes on new significance when viewed through the lens of emotioneering – the practice of systematically crafting product experiences to influence human emotions and perceptions, and increase the chances of people buying the product. Beauty brands and marketers have long recognised the power of shaping what we consider beautiful and desirable. But have you ever stopped to consider why you find certain looks, features or styles appealing?

The Myth of Universal Beauty

At its core, defining beauty standards is a powerful form of emotioneering. The marketing engines and cultural influences that promote certain physical attributes, fashion styles or body types over others directly mould our emotional associations with beauty ideals. Seeing the same narrow standards repeatedly reinforced triggers feelings of aspirational desire or even inadequacy for not meeting those idealised norms.

Mapping Subjective Influences

However, seasoned emotioneers understand that universal beauty is a myth. Perceived beauty is deeply personal, shaped by individual experiences, cultural exposures, and psychological predispositions. By tapping into these subjective influences, brands can emotioneering highly specialised and targeted versions of what “beauty” looks and feels like for different segments. What life experiences or influences have shaped your own concept of beauty?

Crafting Emotional Resonance

For some audiences, rugged, athletic physiques projecting strength and power evoke desired emotions. For others, approachable, lower-intensity looks feel more comfortably aspirational and beautiful. Smart emotioneers study intersections of influences like age, ethnicity, geographical environment, hobbies and belief systems to reverse-engineer the most provocative emotional territory to target.

This principle of crafting emotional resonance extends well beyond just physical appearance into other product realms as well. In the world of software and digital experiences, emotioneers carefully study how different user groups emotionally respond to various design elements, interaction patterns, and functionality.

For instance, an emotioneered secure file-sharing app targeting IT professionals may aim to instill feelings of control, robustness, and authority through its UI and messaging. Conversely, an emotioneered photo editing app for creative consumers might vibe maximalism, playfulness, and unleashed artistic expression. What emotional notes a product strikes shape whether a user perceives it as an innate problem-solving ally or an unsatisfying hassle.

From the interaction micromoments to the holistic user journey, thoughtful emotioneers map the emotional pathways that transform digital bits into resonant human experiences. Do certain software aesthetics, features, or processes amplify your sense of delight, confidence, or creative freedom? The most impactful players understand how to intentionally thread those emotional highlights throughout their digital products.

Imprinting the Beholder’s Eye

Ultimately, while the “beauty in the eye” idiom hints at subjectivity, the most sophisticated emotioneers appreciate that no perspective on beauty is untainted – emotional perceptions around beauty are constantly imprinted, whether by intention or environment. By meticulously mapping the influences and ingrained experiences that shape different beholders’ eyes, emotioneers attain power to systematically shift what emotional notes the idea of “beauty” strikes for any desired audience. Does recognising these influences make you more aware of how your own perceptions may have been shaped?

The Sobering Rarity of Truly Beautiful Organisations

March 6, 2024

Antimatter principle, Article, Business, Culture change, Quintessence

The Sobering Rarity of Truly Beautiful Organisations

In my prrevious post, I discussed how true beauty in software comes from serving human needs and improving lives. This sparked reflections on what defines a truly beautiful organisation. However, a sobering observation is that few organisations even give a passing thought to aspiring to beauty.

Core Purpose

At its core, a beautiful organisation exists to create value for society – actively making the world better through its purpose, products, services, principles and practices. Yet for most companies, this seems an afterthought at best compared to conventional metrics like profits, market share, shareholder returns, and executive wellbeing.

A beautiful organisation has a clearly defined higher purpose to positively impact humanity, not just make money. But how many companies today can succinctly articulate such a purpose that authentically guides all actions and decisions?

The solutions pioneered by a beautiful organisation work to solve real-world problems faced by people, communities and the planet. Sadly, too many organisations avoid grappling with society’s biggest challenges, focused principally on insulating themselves.

Attending to the Needs of All the Folks That Matter™

These rare organisations serve all the Folks That Matter™ – employees, customers, suppliers, owners, and communities – with close attention to their needs, such as respect, equity and dignity. They cultivate diverse cultures of psychological safety where people thrive. Yet most organisations still struggle to move beyond lip service on values like inclusion and general wellness.

Continuous Innovation

A beautiful organisation innovates responsibly in a virtuous cycle of identifying human needs, creating ethical solutions that reveal new needs to address. Compare this to the narrow innovation priorities of most companies centered on products no one needs.

Unlike most firms optimising solely for profits, a beautiful organisation balances success holistically across societal impact, environmental sustainability, stakeholder value creation and financial returns. But how many corporations truly hold themselves accountable to anything beyond the bottom line (in itself a fiction of the first order)?

Comprehensive Transparency

With comprehensive transparency, a beautiful organisation even owns its harmful side effects, those arising despite best intentions. Such radical transparency is unheard of when you consider how most companies obfuscate or greenwash.

Summary

Ultimately, a beautiful organisation is both an exemplary force for good and a successful, profitable business – values and value creation in harmony. Yet this ideal seems an esoteric aspiration most companies comfortably ignore in favor of business-as-usual.

While no organisation is perfect, we might draw inspiration and hope from those rare few striving to improve lives, society and environment through their core purpose and actions The species would benefit from having a greater number of beautiful companies with the vision and courage to embrace this model of making the world better, not just making money.

The True Beauty of Software: Serving Human Needs

Alien tech, Antimatter principle, Article, Attendants, Compassion, Empathy, Philosophy, Product development, Software development, Value

The True Beauty of Software: Serving Human Needs

“Beauty is only skin deep, but ugly goes clear to the bone.”
~ Thomas Overbury

When pondering what constitutes beautiful software, we might choose to look beyond the mere lines of code on the screen. For genuine beauty in software arises not from technical excellence, but from the extent to which it genuinely serves and aligns with the needs of human beings.

A Deeper Beauty

On the surface, we may admire software having clean, elegant code structure, adhering to best practices and exhibiting visual appeal. But the ancient philosophers taught that true beauty must run deeper than superficial appearances. For software, this deeper beauty emanates from how effectively it enhances human capabilities and experiences in the real world.

Power to Elevate

Well-designed software represents the harmonious weaving of digital capabilities with human need. Just as great art inspires by achieving a personal expression of universal themes, so does beautiful software illuminate core human needs through its delivery of cohesive, purposeful functionality. It allows us to appreciate software’s power to elevate and augment our existence.

Like the Romantic poets extolled, beautiful software can facilitate a transcendent union with something greater than ourselves. When developing with insight into human needs, programmers experience a state of flow, bridging the worlds of bits and people until there is no division between the created software and those it benefits. We become co-creators, using our skills to help bring into being solutions which empower.

Resonant

At the same time, beautiful software must resonate with the depth of human experience. As Buddhist wisdom teaches, true beauty arises through mindfulness, ethical conduct, and pacification of the ego. In beautiful software, we find the development team’s consciousness – their thoughtfulness in attending to folks’ needs, their restraint in avoiding the unneeded, their core values embodied in the system’s behaviours.

Inner Light

Moreover, beautiful software exhibits an inner light not of technical correctness, but of purpose – solving real human needs with clarity and compassion. Its beauty transcends being well-crafted to also being virtuous, ethical and generous in spirit. For its core purpose is selfless service to humanity.

Conclusion

So while we may appreciate the external trappings of high-quality software, true beauty runs deeper – into how well it elevates human potential and adapts seamlessly into the real needs of peoples’ lives. For therein lies the highest achievement, to create not just products, but solutions that illuminate, attend to, and empower the human condition.

The Power of Reflective Questions

Actionable Insights, Article, Capability development, Collaboration, Community, Conversations, Culture change, Dialogue

The Power of Reflective Questions

The Impact of Our Questions

When it comes to understanding employee satisfaction and well-being, the questions we ask hold immense power. They shape the depth of insight we receive and the degree of self-reflection they prompt in others.

Simple vs. Reflective Questions

Consider these two contrasting questions:

“Do you feel happy in your work and workplace?”
“What factors contribute to making you feel happy or sad about your work and workplace?”

The first question stands broad and surface-level. A simple yes/no response fails to encourage any deeper self-reflection on the part of the employee. While they may respond truthfully, that single word provides no window into the nuanced drivers behind their feelings. Some might describe this as a “closed” question.

The second question, however, demands thoughtful introspection. It pushes the employee to pinpoint the root causes and specific elements that amplify or detract from their workplace fulfillment and positive sentiments about their role. Some might describe this as an “open” question.

The Value of Self-Reflection

An insightful response might go:

“I find happiness in this role’s meaningful work and growth opportunities. However, the long hours, lack of work-life balance, and poor management communication leave me frequently stressed and discouraged.”

This level of self-reflection yields far richer insights for the employer and embloyee, both. They gain a holistic view into not just the employee’s mood, but the underlying factors and pain points shaping their experience each day.

Fostering Authentic Understanding

The quality of the questions we ask directly impacts the quality of self-reflection. When we ask binary, closed-ended questions about complex issues like happiness, we restrict the potential for enlightening personal contemplation, and meaningful dialogue.

In contrast, open-ended exploratory inquiries serve as prompts for valuable self-reflection. They require respondents to purposefully examine their emotions, motivations, and the nuanced elements influencing their attitudes and engagement levels.

As employers, if we seek authentic understandings rather than superficial sentiments, we must create room for self-reflection through our questions. Instead of asking “Are you happy?”, we might choose to frame inquiries that facilitate thoughtful exploration: “What brings you a sense of meaning and fulfillment in your work? What factors leave you feeling dissatisfied or burnt out?”

The Path to Better Connection

When we invite this level of self-reflection, we don’t just understand an employee’s current state. We gain powerful insights into the roots of their experiences – both positive and negative. Armed with that deeper awareness, we can enact changes, reinforce strengths, and directly address issues eroding engagement and achievement, and sucking joy.

In the quest for connection, self-reflective questions are an under-utilised superpower. They enable not just data collection, but a purposeful exploration of the human experience we’re aiming to improve. Let’s craft questions that illuminate richer truths and inspire more fulfillment.

Chatbots Make Blogging Easier

AI, Article, Writing

Chatbots Make Blogging Easier

Writing quality blog posts consistently can be a challenge, especially when you’re short on time or struggling with writer’s block. But what if you had an intelligent assistant to help streamline the process? Enter Claude, the AI chatbot that can be a game-changer for bloggers. (Note: You may, quite reasonably, favour another Chatbot).

Here’s how you can leverage your favourite Chatbot’s capabilities to enhance blog post writing:

Ask your Chatbot to Write A Blog Post
The first step is simple – ask your Chatbot to write the blog post for you based on the topic, angle, and any specific guidelines you provide. You can be as vague or detailed as you like with your prompt. Your Chatbot will then generate an initial draft pulling from its vast knowledge base. (Hint: you may want to ask it to include subtitles for each section).
Review and Refine
Once you have the draft, read through it critically. Identify areas where your Chatbot may have missed the mark or misinterpreted your intent. Don’t worry, that’s perfectly normal when working with AI.
Request Rewrites (Iteratively, As Needed)
If there are significant shortcomings, go back to your Chatbot and ask it to rewrite the post while providing it with more context, direction and specific feedback. You may choose to go through a few iterations until the post accurately captures your vision.
Edit for Polish
Once you’re satisfied with the substance of the AI-generated draft, it’s time for you to apply your uniquely human touch. Edit the post (i.e. outside the Chatbot) to refine the language, smooth out transitions, eliminate AI tripe and hallucinations (especially in attributions, quotes, references, links, and etc.), inject your unique voice, and align it with your blog’s tone and style.
Copy Editing (Optional)
Pass (paste) the post back into the Chatbot and ask it to correct for typos, spelling errors, grammar, tone, etc.
Enhance with e.g. Visuals
Don’t forget to complement your polished post with relevant visuals and such that catch the reader’s eye. While your Chatbot can suggest ideas, you’ll want to carefully select or create images, graphics, and media that elevate your content’s appeal.
Publish and Promote
After putting in the finishing touches, you’re ready to publish your AI-assisted blog post and share it with the world through your regular promotion channels.

The beauty of using a Chatbot is that you can adaptively exploit its skills based on your needs. For some posts, you may only need a rough draft to build upon. For others, you could have your Chatbot handle most of the heavy lifting and just need to apply the final polish.

So why not give e.g. Claude a try (I find the free version more than enough, most days) and experience how an AI co-pilot can revolutionise your blogging workflow? You may be surprised at how this smart assistant helps you create more compelling, high-quality content in a fraction of the time.

P.S. You may have reservations about the quality of chatbot “writing”. I’ve used the approach described above, almost exclusively in writing my posts here on Think Different, since December 2022. I’ll let you be the judge as to the quality of writing it deliivers.Your feedback, comments and questions are welcome!

Seniority

Article, Business, Capability development, Experts, Fellowship, Genius, Software development, Systems thinking, Teambuilding

Actionable Insights, Article, Business, Culture change, Organisational effectiveness, Organisational Therapy, Paradigm shifts

Seniority

The labels “junior,” “mid-level,” and “senior” get batted around frequently. But the true hallmark of a senior has nothing to do with the years under their belt. Rather, it’s about having gained the ability to introspect, adapt, and apply hard-won lessons from seeing a multitude of challenges and scenarios.

The Path is Lit by Diverse Problem-Solving

What most sets senior developers, engineers, and business folks apart from the less senior is the wealth of different problems they’ve encountered and the innovative solutions they’ve seen, and crafted. They’ve grappled with issues spanning:

Appreciation for a System: This involves understanding how various components within an organisation or community interact with each other. It emphasises looking at an organisation as a whole system rather than isolated components. It also stresses understanding how actions and changes in one area can impact other areas.
Theory of Knowledge: This relates to the concepts around how learning and knowledge acquisition take place. It covers topics like operational definitions, theory of variation, psychology, and a theory of learning. The aim is to guide learning, decision making, and organisational practices.
Knowledge about Variation: This involves understanding variation, both controlled (common cause) and uncontrolled (special cause) variation. It stresses using statistical thinking and tools to study process variation over time and identify the root causes of variation.
Knowledge of Psychology: This refers to an understanding of human behavior, motivation, and interactions between individuals and circumstances. It emphasises cooperation, learning, fellowship, and driving out fear from the workplace to enable intrinsic motivation.

This diversity of experiences has hewn true wisdom – the ability to rapidly explore roots of problems, innovate novel approaches, predict potential pitfalls, and maintain a flexible mindset. The path to seniority is illuminated by persistent introspection, asking “What worked?” “What didn’t?” “How can we apply those learnings going forward?”

A Cross-Functional Vision Emerges

By being immersed in a vast array of problems across multiple domains, senior people begin to connect the dots in a profound way. They gain a systems-level view that transcends any single function or specialisation.

A senior software person isn’t just a coding guru, but someone who understands development, QA (and the real meaing of the term), infrastructure, security, and how technology drives business impact. A senior business person doesn’t just regurgitate methods from an MBA textbook, but can intuitively design strategies that harmonise sales, marketing, product, and operations.

This comprehensive vision allows seniors to participate fully in high-level initiatives, make strategic decisions, and provide indispensable coaching substantiated by their own intense introspection over years of learning experiences.

Crucibles of Collaboration and Wisdom Sharing

The most impactful senior roles aren’t just about solving problems, but about spreading the philosophy of how to solve problems. The most valuable senior folks spread their hard-won wisdom across different teams, departments and the whole company. They invite people into an environment where all can learn and grow together.

Through mentoring others, sharing knowledge, working side-by-side and illustrating by example, seniors pass on the deep lessons they’ve digested from their experiences. While juniors focus on mastering specific tools and skills, seniors aid people in truly understanding how to creatively solve problems together.

Instead of hoarding their years of practice, the best seniors are generous in distributing their insights organisation-wide. Their goal is contributing to building a cadre of brilliant problem-solvers who see challenges as opportunities to get smarter.

Through mentorship, knowledge shares, pairing, exemplars, and other means, seniors seed their problem-solving approaches – ways to deeply inspect issues through multiple lenses, devise innovative approaches, and continuously introspect for improvement.

The most valuable seniors aren’t fogeys hoarding years of experience, but diligently introspective learners aiding others to illuminate their own wisdom through the challenges they face. Seniority is about leaving a trail of proble solvers in your wake who redefine challenges as opportunities to grow.

An Introspective Mindset, Not an Age Metric

At the end of the day, being considered “senior” is about evolving a mindset – not just logging years of experience. It’s about diligent introspection, ceaseless curiosity when encountering new challenges, and proliferating learned lessons for collective growth.

The best senior people don’t see their years as a sign of fading abilities. Instead, it represents a brilliant path of practical wisdom gained by treating every problem as a chance to expand their skills and knowledge.

Being truly senior is the result of carefully developing the rare talent of learning how to learn effectively. Rather than resting on their experience, impactful seniors relentlessly find ways to push their understanding further when facing new challenges.

Their years doesn’t mean they’re past their best – it shows they’ve mastered constantly improving themselves by tackling problems head-on. Seniority comes from nurturing the exceptional power of turning obstacles into opportunities for growth, and knowing that their best is just out of reach, and ahead.

The Seductive Allure of Command-and-Control

March 4, 2024

The Seductive Allure of Command-and-Control

Defining Command-and-Control

In the context of business organisations, command-and-control refers to a top-down, highly centralised management approach. It is characterised by strict hierarchies, rigid processes and procedures, and a focus on enforcing compliance through rules and policies set by senior management.

Under a command-and-control model, strategy and decision-making flow vertically downwards, from the top, with managers and executives dictating priorities and objectives that must be executed down the chain of command. Employees have little autonomy or latitude for questioning directives from above.

The Lure of Execution

We all want to get things done effectively and efficiently. As humans, there’s a deep satisfaction in seeing our efforts translated into concrete results. Whether it’s getting that big project shipped, launching a new product, or just ticking items off our personal to-do list, achievement feels good.

However, in many organisations, the primacy placed on “getting things to work” can blind us to deeper systemic forces at play. All too often, the siren song of efficiency and execution drowns out more fundamental questions about whether we’re even working on the right things in the first place (a.k.a. effectiveness).

Institutional Inertia

The truth is, large organisations are complex systems governed as much by unspoken assumptions, ingrained beliefs, and social incentives as any official policy or executive mandate. The very rubrics we use to measure success – be it revenue targets, user growth, or other metrics – emerge from a particular culturally-entrenched worldview.

Within this context, a command-and-control narrative reigns supreme. We optimise for top-down directives, vertical hierarchies, and centralised decision-making. Goals get cascaded down, while accountability and compliance permeate back up the chain. Efficiency and order and managers’ wellbeing are prioritised above all else.

The system effectively hard-wires this command-and-control mentality. Being a “team player” often means deferring to established processes, not rocking the boat, and falling in line with conventional thinking. Those who push back or challenge assumptions are frequently sidelined as “not pragmatic” or “not working towards the same priorities.”

The Costs of Control

Things get done, to be sure. But at what cost? A singular focus on execution often means unquestioningly working towards the wrong objectives in the first place. It breeds an insular, institutionalised mindset that is exquisitely efficient…at preserving the status quo.

Perhaps more importantly, a command-and-control culture discourages the very creativity, critical thinking, and experimentation needed for an organisation to truly adapt and evolve over time. After all, what incentive does anyone have to question the deepest assumptions that underlie day-to-day work when doing so could threaten their standing, compensation, and career prospects?

Catalysing Change

True change requires creating space for fundamentally rethinking and reimagining what an organisation is optimising for in the first place. It means giving voice to diverse perspectives, nurturing a willingness to exploit fleeting opportunities and take calculated risks, and embracing a degree of productive failure.

Dismantling existing systems is hard, uncomfortable work. Doubly so for dismantling entrenched assumptions and beliefs. It inevitably encounters inertia and opposition from those who are vested in maintaining the current order. But simply getting things done is not enough – we must wrestle with whether we’re even pulling the right levers to begin with.

To catalyse genuine innovation and transformation, we might choose to move beyond blind adherence to the siren song of pure execution. We must create the conditions for all voices to be heard, for first principles to be questioned, and for fundamentally new visions and possibilities to emerge. Only then can we achieve meaningful change.

The Power of Beliefs

March 3, 2024

Article, Business, Collective psyche, Culture change, Organisational effectiveness, Organisational Therapy, Paradigm shifts, Quintessence, Rightshifting