The Visionary Notion

What if the primary driving force behind commercial and economic endeavors wasn’t the pursuit of profits, but rather benefiting society, the species, Gaia, and the planet? A visionary notion, to be sure, that seems to defy conventional capitalist wisdom. Nevertheless, if we allow our imaginations to roam freely and look back at periods in history where ethical business practices held sway, we can depict a world truly transformed by this paradigm shift.

Profit Motives vs. Ethics and Humanity

Throughout most of human history, the profit motive has reigned supreme in the business realm. However, there have been notable exceptions driven by religious teachings, philosophical movements, and social ideals that prioritised ethical conduct over mere grubby accumulation of more and more wealth. The Quakers, for instance, were renowned for their commitment to honest dealings and consideration of employee welfare, exemplified by the socially-conscious British chocolate makers like Cadbury. The 19th century cooperative movement aimed to create enterprises that equitably shared profits with worker-owners and the local community.

The Beauty of Ethical Business

Would we call businesses truly putting the greater good before profits “beautiful”? At first, such a description may seem like an odd coupling of aesthetics with commerce. But perhaps there is an inherent beauty to enterprises that create sustainable value for society while exhibiting ethical conduct.

Just as we find natural wonders, artistic works, or selfless acts emotionally moving due to their harmony with higher ideals of truth, goodness, and transcendence of ego, so could businesses centered on benefiting all stakeholders embody a different kind of beauty. One not necessarily based on physical appearance, but on being skillfully crafted exemplars of how our economic activities can align with ethical, aesthetic, environmental and humanitarian principles.

This beauty manifests through their products, services, and operations, harmonising with the world rather than undermining it through greed, despoilment, or exploitation. Beautiful businesses are sustainable and circular by design, creating goods to be celebrated and cherished rather than cynically designed for disposability.They invest in creating opportunity and dignity for workers and communities rather than grinding them underfoot for profit margins.

Where today’s shareholder-driven corporations often exemplify grotesque machineries of extraction, ethical enterprises putting people and planet over money could be sublime new exemplars of applied aesthetics – aspiring toward perfection not through profit metrics, but through positively impacting all they engage with. Their beauty would shine through in becoming tightly interwoven threads in an interdependent tapestry, creating joyful, resilient and regenerative systems that elevate our shared potential.

While the traditional business vernacular focuses on the uglyness of lucrative processes, revenue growth, and reputational brand value, a world where ethical enterprises reign would celebrate hallmarks of perfected form: generative models that produce societal good, environmental integrity, attending to folks’ needs, and uplifting the human spirit. Perhaps then, we could appreciate the highest “good companies” not just pragmatically, but aesthetically – as living artworks of conscious, ethical organisation.

A World Oriented Toward the Greater Good

In such a world oriented toward the greater good, companies measure success not just by financial returns, but by positive impacts. Ethical practices like those espoused by certain faith traditions and thinkers are the norm across these industries. Sustainability is prized over short-term gain, with environmental stewardship prioritised over resource exploitation. We’ve seen glimpses of this in recent decades through the rise of corporate social responsibility (CSR), socially conscious investing, and the emergence of benefit corporations legally bound to creating public benefit, not just profits. But such examples have remained the exception rather than the rule in a profit-driven system.

The Global Ethos of the Greater Good

Imagine if this ethos becomes the core operating principle globally. Rather than lobbying for narrow interests, these businesses advocate for the common good. Tax avoidance schemes would be abandoned in a system where contributing one’s fair share is the ethical baseline. Worker rights and equity are vigorously protected, not eroded in pursuit of higher margins. On an individual level, cutthroat workplace could gives way to healthier cooperation, and integration with our personal and community values and family lives. Ethical conduct is rewarded over pure profit-generation at any cost. Kudos is not derived from endless growth metrics, but to positive impacts created for all the Folks That Matter.

A Sustainable Economic Model

Of course, enterprises still need to generate income to remain viable and reinvest in their social missions. But growth is pursued by creating genuine value for society rather than extracting it. Sustainable, circular economic models replace those premised on endless consumption and planned obsolescence.

A Radical Yet Possible Vision

Such a world may seem naively idealistic to modern sensibilities, conditioned to accept profit as the prime directive. But is it any more far-fetched than an entrenched global system that relentlessly exploits people and finite resources in pursuit of perpetual economic expansion on a finite planet? By orienting business toward the greater good, as past ethical movements have done, we might create an economy that better serves humanity. This may read as a utopian ideal today, but it has been a reality at various points throughout our history. A world where businesses prioritise society over self-interest may not be inevitable, but it is possible if we dare to imagine and build it together.

Do you have even the briefest five minutes to contemplate how things might be different?

Further Reading

Ackoff, R. L. (2011). The aesthetics of work. In Skip Walter’s blog post retrieved from https://skipwalter.net/2011/12/25/russ-ackoff-the-aesthetics-of-work/

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

1. 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.

2. 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.
3. 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.
4. 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.

5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.
11. 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.
12. 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.
13. 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 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:

1. 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.
2. 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.
3. 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.
4. 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 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.

Teams that are capable of smoothly and swiftly reconfiguring themselves is becoming the norm in the software industry today. Rather than old-fashioned rigid structures and siloed employees, progressive organisations opt for a more fluid approach that allows for responsiveness to shifting conditions.

Team members work across multiple projects in these flexible arrangements, contributing versatile skills as needed and rearranging team composition to suit the task in hand. Situational leadership – a.k.a. Fellowship – emerges based on expertise instead of formal titles. With boundaries that allow copious and timely information sharing between interlocking teams, rapid coordination becomes commonplace.

Self-direction and mutual trust enable these dynamic teams. A strong, shared strategic purpose coupled with developmental training and organisational support gives members the confidence to take initiative without constant top-down control. Teammates understand how their piece connects, empowering local decision-making even as larger configurations reshape around evolving challenges.

This fluid team format creates adaptable organisations capable of smooth reprioritisation as demands change, unencumbered by bureaucratic processes. People, ideas and resources flow to each new focus area in turn, adjusting teaming patterns seamlessly to current priorities. Progress keeps pace with the opportunities and demands of the day.

Some continuity and purposeful guidance balances out the flux. Respected, experienced figures may anchor successive teaming waves, providing continuity of culture and knowledge transfer. As thought leaderBob Marshall describes in his acclaimed book ‘The Team Fruit Bowl’, fluid teams’ steadiness enables ongoing realignment around the organisation’s North Star.

Self-aligning, versatile teams represent the leading edge of organisational design today. Staying responsive without getting swept away, they ride currents of change toward transformative performance.

Rigour refers to the strict precision and accuracy with which work is executed in fields like software engineering and collaborative knowledge work (CKW). It entails adherence to standards and best practices for needed outcomes.

The Importance of Getting it Right

Attentive rigour matters because carelessness breeds mistakes. Flaws in logic or bugs in code stem from a lack of rigour. This introduces unwanted surprises, and failures down the line. Rigour is an attitude of mind that zeroes in on getting things right the first time Cf. Crosby, ZeeDee.

The Perils of Getting it Wrong

However, the quest for rigour can go awry when imposed hastily or mindlessly. Establishing rigorous frameworks like requirements analysis, peer review etc. does carry overhead. Teams can get so bogged down chasing perfection that creativity, productivity and morale suffer. Or so much time is spent eliminating small defects that bigger picture progress slows. Like most things, balance is warranted.

The Laissez-Faire Extreme

At the other end of the spectrum from rigour lies the laissez-faire attitude. This French phrase meaning “let it be” encapsulates a laid-back approach where participants have broad freedom to work in whatever manner they choose.

In software and knowledge work contexts, laissez-faire environments feature very few enforced policies, protocols, or mechanisms for ensuring quality. Creativity and unhindered workflow takes priority over rigour. Peer reviews, quality assurance, and documentation are optional. Teams self-organise organically without work standards.

This spontaneity can spark innovation but has pitfalls. Lack of rigour tacitly permits cut corners, gaps in logic, unfinished ideas and sloppy execution. With an easy-going approach, easily preventable flaws accumulate and undermine end results.

In applied contexts like commercial software development, laissez-faire practices practically guarantee shoddy work products riddled with defects. User needs demand rigour not as an obstacle, but as an enabler of excellence. Finding the right balance is key.

The absence of rigour embodied in laissez-faire philosophies may promote freedom. But the ensuing chaos leaves the fruits of hard work easily compromised. Some structure and rigour ultimately serves applied collaborative knowledge work better in the long run.

While cutting corners is not an option, forced rigour without context can mean marginal gains at disproportionate cost. Rigour must enable, not encumber, the pursuit of excellence. Teams that foster a culture where rigour flows from all participants, intrinsically and voluntarily, tend to find the sweet spot. Getting there requires clarity of purpose, patience, and care. Do that and rigour lifts the quality of collaborative knowledge work substantially over time.

What does rigour mean to you and your team?

Work dynamics have been evolving rapidly in recent decades. Back in 1959, management expert Peter Drucker coined the term “knowledge work” – jobs focused more on expertise application versus manual tasks. Today, many observe the economy shifting from industrial production to innovation through agile collaboration.

Fundamentally Different

The nature of work has fundamentally changed. We have shifted from an industrial economy largely based on manual labour to a knowledge economy increasingly based on intellectual collaboration. This transition invites a new way of looking at work, focused on both recognising and facilitating collaborative knowledge work (CKW).

In this model, cross-disciplinary teams come together to brainstorm and refine breakthroughs iteratively. Silos give way to fluid circles of contribution. Motivation stems intrinsically from the shared mission, not extrinsic rewards. Experimenting with unconventional ideas bears lower risk when paired with constructive peer feedback.

But embracing the CKW paradigm depends on adopting a distinctly different approach to work. How can groups establish norms where everyone feels comfortable contributing without fear of judgement or rejection?

Autonomy, Mastery and Shared Purpose

Part of the solution links back to aligning clearly around higher purpose. When autonomy coexists with shared accountability, inspiration untaps. Structuring reciprocal mentorship allows members to develop emotionally and motivationally while exchanging honest developmental guidance.

This differs drastically from the hierarchical command-and-control management style of the past century that was well-suited for manual labour but proves limiting for knowledge work. Managers can no longer simply dictate tasks and expect compliance. For collaborative efforts to thrive, managers must nurture a culture that empowers teams with autonomy while providing direction, support, and facilitation.

What About Management?

Those in the know recognise the incompatibility of CKW and the traditonal management paradigm. Yet, organistions intent on making the best of CKW are faced with transitioning away from the concept of management towards e.g. sefl-managing teams and fellowship. In essence, we’re talking about culture change. Here’s some guidance in that regard:

Guidance for Old-Guard Managers

For managers used to traditional modes of top-down management, adopting a collaborative approach invites a paradigm shift. Here are key ways to enable more participatory and productive knowledge work:

• Provide transparent context and clarity around broader goals while giving teams discretion in determining how goals are achieved.
• Cultivate constructive exchanges where all team members feel comfortable contributing ideas without fear of judgement.
• Ask probing questions, identify gaps, and point to resources, not dictate solutions.
• Focus on facilitating the collaborative process through conflict resolution, dialogue around communication norms, and adaptive coordination.
• Champion new ideas that arise from the team and rally support across the organisation.
• Evaluate performance based on the effectiveness of collaborative processes and quality of outputs.

Advice for New Managers

For those assuming their first management role, the collaborative approach may feel more intuitive. Still, translating intent into impact invites concerted learning. Here are some areas for new managers to consider:

• Foster emotional intelligence to nurture relationships, understand different working styles and motivations, and resolve interpersonal friction.
• Hone facilitative teambuilding techniques like liberating structures, engagement through powerful questions, and conversation mapping.
• Promote inclusion by valuing diverse voices, ensuring equal opportunity for contribution, and mitigating dominant perspectives.
• Develop fluency in digital collaboration tools and appropriate applications for remote and hybrid work settings.
• Elevate and practice orchestrating for collaborative work.
• Pay attendtion to the quality of interpersonal relationships and the overall social dynamic.
• Attend to folks’ needs.

The CKW paradigm brings substantial promise and possibility but requires managers themselves to transform. By embracing this challenge, leaders can unlock unprecedented potential from today’s knowledge workers.

The future lies in fully unleashing human potential by connecting talent to shared missions. But practical change management matters. How might we reinvent team rituals and processes to make this vision an everyday reality? The answers will come collaboratively, through commitment to the journey of learning together.

The driving purpose behind most of my 1000+ blog posts here on Think Different is exploring how we might collectively foster environments that enable people to give of their best.

What if we created workplaces and environments where everyone feels respected, trusted, and intrinsically motivated to do meaningful work? How could empathy, compassion and vulnerability strengthen teams?

Imagine prioritising inspiration over control, coaching over criticising, unlocking potential over punishing failure. What could empathic structures, self-direction and flexibility allow us to achieve together?

Fire All the Managers

In his thought-provoking 2011 HBR article “First, Fire All the Managers”, Gary Hamel makes a compelling case for phasing out managers entirely. He argues that hierarchical management structures inhibit agility, innovation, and engagement. While eliminating management altogether seems radical, Hamel raises important points on rejecting traditional collective assumptions and beliefs about management.

Exponential Achievement

This journey requires examining collective assumptions, taking risks and pioneering new models. It may mean temporary discomfort yet enables exponential human achievement.

I don’t claim to have all the answers. But the invitation is open – to walk together toward enlightened working, one thoughtful experiment at a time. To choose fellowship over hierarchy, vision over rules, and nonviolence over Fear, Obligation, Guilt and Shame.

Enormous Possibilities

Progress won’t happen overnight. The path involves stumbles yet holds enormous possibility. My hope is my Think Different posts help spark insight and courage to create environments where every person can thrive.

What ideas do you have on this journey? What approaches resonate with you? By sharing perspectives, we discover the way forward together. The destination can best be uncovered collaboratively.

Feedback

Let me know if this resonates as an inviting post tying back to my core focus on human-centered environments while headlining the overall purpose of this long-running  blog. I appreciate you encouraging and supporting me to refine the framing and messaging!

Management, often viewed as the backbone of an organisation, faces its own set of challenges. Despite the numerous management models that promise streamlined operations and workplace efficiency, something isn’t quite right. Surprisingly, the dissatisfaction emanates not just from the employees but significantly from the managers themselves.

What’s Causing the Discontent?

Various factors contribute to the malfunction of traditional management approaches. One significant factor is the constant need for control, which limits everyone’s creativity and self-expression. Then there’s the stress and burnout stemming from never-ending deadlines and performance evaluations. It’s not just the team that’s under pressure; the manager feels the heat just as much, maybe even more so.

Are Traditional Approaches Outdated?

Traditional management methods rely on hierarchical models that do not align with today’s rapidly evolving business landscape. These models leave little room for flexibility and adaptation. While they might have worked in a different era, they fail to cater to contemporary workplace dynamics that value collaboration, knowledge work, and open communication.

How Does the Management Paradigm Affect Mental Health?

Mental health concerns are no longer a peripheral issue. When management methods focus solely on performance, they fail to consider the psychological well-being of the individuals involved, including the managers themselves. Anxiety, stress, and a lack of work-life balance become the unintended byproducts of such methods.

Is There a Solution?

Rather than adhering to management, ever more ineffective, organisations might choose to explore alternative ways of directing, coordinating and resourcing the work. These could include flat organisational structures, self-organising teams, fellowship, and even organisational psychotherapy – to tackle inherent workplace issues at their core. These approaches place people over metrics, and folks’ needs over numbers, thereby leading to a more humane working environment.

Is Change Really Possible?

Change often mets with resistance, especially when it threatens conventions and long-standing practices. However, the increasing awareness of the limitations of conventional management is a signal that change isn’t just needed; it’s inevitable. As more organisations shift their focus from stability, conformance and costs, to overall well-being, we may finally see that management isn’t working, and this has been so for a long time now.

Summary

In sum, for organisations to rightshift towards be true effectiveness, it invites a profound reevaluation of the role of management. The shift will be towards more flexible, people-oriented approaches that don’t sacrifice human well-being for the sake of efficiency, stability and conformance. Only then can we hope for a work environment where both the employees and the (ex)managers both thrive together.

What’s Truly Happening in Our Offices?

Many workplaces are entangled in a web of complexities, often driven by politics, power dynamics, and individual ambitions rather than motherhood-and-applie-pie ideals like trust or shared goals. Given this landscape, AI doesn’t just enter as a neutral tool; it has the capacity to significantly influence these existing dynamics.

Is AI a Participant or a Bystander?

As AI infiltrates more and more aspects of work, its role is anything but passive. Transparency in how AI is implemented and utilised matters. A transparent approach helps to build trust by making it clear how AI influences decisions, from hiring to performance evaluations. This can prevent the perception of AI as an omnipresent ‘big brother’.

Can AI Ameliorate Workplace Bias?

AI systems have the power to either reinforce or alleviate existing biases, depending on how they’re applied and what data they’re fed. To avoid perpetuating stereotypes or inequalities, regular audits of these systems can help identify any skewed algorithms or biased data sets. Implementing corrective measures ensures fairer outcomes.

How Do We Strike the Balance in Communication?

AI tools can risk making interactions among team members more transactional and less personal. A balanced approach might involve utilising AI for mundane tasks like scheduling or data sorting, while preserving human interactions for tasks requiring emotional intelligence and nuanced discussion. This dual approach aims to enhance productivity without sacrificing the quality of interpersonal relationships.

Where Are the Ethical Boundaries?

AI raises fresh ethical questions around data privacy and employee surveillance. These aren’t just technical issues but deeply human concerns that can affect trust and morale. Establishing a clear ethical framework for AI usage can go a long way in reassuring employees that their data won’t be misused and that AI tools are in place to assist rather than monitor them.

Will AI Reshape Office Hierarchies?

As AI gains the capability for data-driven assessments, the entire concept of hierarchical structure in workplaces could face a radical change. If we move away from promotions and role assignments and instead focus on team dynamics and systems contributions as captured by AI analytics, a more egalitarian environment could emerge. This shift disrupts established power dynamics and allows for a culture based on collective contributions rather than individual titles.

What’s the Inescapable Impact?

The influence of AI on the existing dynamics of the workplace is inevitable and multifaceted. It’s not just about technological changes but shifts in culture, ethics, and interpersonal relations. By consciously addressing these aspects, an organisation can guide the impact of AI towards creating a more transparent, equitable, and effective workplace that truly begging to address the needs of all the Folks That Matter.

Life can be a labyrinth of responsibilities, expectations, and emotions. Amidst the maze, it’s easy to lose sight of folks’ fundamental unattended-to needs. Or even that people have more wonderful lives when their needs receive attention – from e.g. friends, family, employers and coworkers.

Broaching these questions with a close friend could be your mutual ticket to helping each other have more wonderful and satisfying lives:

1. “What Are The Things – If Any – You’d Like to Have Happen (that aren’t happening yet)?”
   Discussing desires and aspirations that haven’t yet come to fruition can open up new possibilities for growth and satisfaction. It could even illuminate areas where friends, etc., can support each other to make life more wonderful.
2. “What Gives You the Sense That Something Is Missing?”
   This sensation of something being amiss is not uncommon. It’s like a jigsaw puzzle with a missing piece; you can see the overall picture, but in some way it’s incomplete.
3. “What Differences Do You Notice Between Your Current Life and Something Better?”
   Here’s an opportunity for reflection. There’s often a discrepancy between our lived experiences and our ideal lives. Acknowledging this disparity might help in closing the gap.
4. “What Needs Haven’t You Shared Out Loud?”
   We all have those unspoken wishes—perhaps because they seem too foolish or unreachable. Yet, acknowledging these can be the first step toward addressing unmet needs or goals.
5. “What Haven’t You Done Yet?”
   Procrastination, or even just life getting in the way, can keep us from pursuing things we’re passionate about. What’s on your list of ‘somedays’ that you might turn into ‘todays’?
6. “What Makes You Feel Understood or Misunderstood?”
   The emotional nourishment that comes from being understood is a fundamental human need. If it’s missing, that’s something worth exploring further.
7. “What Topics Find You Changing the Subject?”
   Sometimes avoidance is the best indicator of significance. Those undiscussable topics or issues you’re sidestepping? They could be precisely where attention is most needed.
8. “How Do You Feel When You Have to Say No?”
   The difficulty in setting boundaries is often symptomatic of deeper, unattended needs. If you find it challenging to say no, this might be an area worth investigating.
9. “Where in Your Life Do You Feel Like You’re on Autopilot?”
   Routine can offer comfort, but it can also veil unmet needs. If you find areas of your life running on autopilot, it could be a sign to probe deeper.
10. “What Emotions Do You Find Yourself Keeping in Check, or Burying?”
    Society often prescribes what emotions are acceptable, causing us to suppress those that aren’t. These suppressed emotions could point to neglected needs or aspects of oneself.

Discussing these questions may not offer quick fixes, but they can pave the way for deeper and more rewarding connections with others. Of course, this all hinges on genuine concern for the people you’re conversing with. Without empathy and compassion, these conversations are vacuous at best.

The Managerial Role: Obsolete

Traditionally, managers serve as overseers, ensuring work flows smoothly and deadlines meet their marks. But in today’s business environments, we’re seeing a seismic shift. Teams are self-organising and making decisions independently. Why do we still need managers?

Do Teams Manage Themselves?

The answer seems to lean towards ‘yes’, teams can and do “manage” themselves. In settings where productivity is of the essence, the emphasis is on empowering teams to solve problems and innovate without having a managerial figure present, breathing down their necks. Collective ownership becomes the mantra, and everyone takes responsibility for the product’s success or failure.

What Happens to Accountability?

Contrary to popular belief, the absence of a traditional managerial role doesn’t mean accountability vanishes. In fact, team members often feel more accountable to each other than they might to a distant or toxic boss. Review processes become more meaningful, as peers understand the challenges and intricacies of the tasks at hand.

Is Decision-Making More Efficient?

The chain of command usually slows down decision-making. In a manager-less environment, teams arrive at decisions more quickly and can adapt to changes or unexpected challenges without having to wait for managerial approval. This can be especially vital in the fast-paced world of software development. See also: Auftragstaktik.

Does Quality Suffer?

One concern is that without a managerial figure to enforce standards, quality might slip. However, evidence suggests that the opposite happens. A sense of ownership and peer review often leads to a higher standard of work. Team members become each other’s quality control, leading to a more cohesive and well-executed end product. See also: Ensemble development.

What’s the Role of Leadership?

Leadership doesn’t evaporate in the absence of managers; it merely takes a different form. Leaders emerge naturally, guided by their expertise, communication skills, context, and the team’s respect. These leaders are often more in tune with the needs and dynamics of the team, making for a more harmonious and productive work environment.

Is This Model for Every Business?

The manager-less model isn’t just a passing fad in the software development world; it raises legitimate questions about the universal need for managers across all business types. While some argue that industries with stringent regulatory compliance or high-volume customer interactions need a managerial structure, this reasoning often serves as a convenient crutch rather than a real justification.

Firstly, regulatory compliance doesn’t inherently require a managerial role. Businesses can still adhere to laws and regulations through well-documented processes and collective responsibility. Teams can be educated and empowered to include regulators in the set of Folks That Matter and comply with rules without a manager acting as the gatekeeper.

Secondly, the idea that customer service businesses benefit from managerial roles is also questionable. Frontline employees are more likely to understand the intricacies and nuances of customer interactions than a removed managerial figure. Empowered teams often show better problem-solving capabilities, which is beneficial in handling complex customer concerns.

So, are managers necessary? The evidence increasingly points to ‘no’. Even outside the tech sector, rethinking the need for managers can lead to more agile, responsive, and accountable businesses.

So, Are Managers Redundant?

In the context of modern software development and certain types of businesses, managers are increasingly looking like relics of a past era. For businesses willing to take the leap, a manager-less structure offers more than just cost savings; it paves the way for innovation, efficiency, and a far more engaged workforce.

Further Reading

Zanini, M. (2021). Can we manage without managers? Retrieved on 9 September 2023 from https://www.michelezanini.com/can-we-manage-without-managers/
Zanini, M. (2014). Companies without managers better every metric. Retrieved on 9 September 2023 from https://www.cobrt-archive.com/archived-blog/2014/08/companies-without-managers-better-every-metric/

Who’s In Charge?

For years, companies have automatically installed managers at the helm of software development teams. Why? Perhaps it’s because this model has been employed across various other industries with some semblance of success. But is this the right approach for software development?

Does Archaism Matter?

Historically, the concept of a manager has roots in the Industrial Age, where assembly lines were all the rage. These lines seemed like they needed supervision and structure. The manager became the linchpin in ensuring that production flowed more or less smoothly. While this may have worked in a factory setting, software development isn’t assembly work. It’s more akin to crafting a work of art. So why are we still clinging to archaic notions?

What Devs Need

Developers don’t need someone hovering over them, dictating their every move. They need autonomy and space to innovate. Software development is a field that requires creative thinking, problem-solving, collaboration, and an in-depth understanding of technologies. These skills can’t be micromanaged into existence. Instead, a supportive, collaborative environment is more beneficial. So, if not managers, then who or what can create such an environment?

Why Not Self-Management?

Self-management or self-organising teams are a game changer in the software development industry. Such teams have no formal manager but work towards a common goal. Every team member is responsible for managing their tasks and collaborating with their teammates. While this model isn’t flawless, it’s more attuned to the needs and work style of software developers, and collaborative knowledge work more generally.

There Are Alternatives

If going manager-free feels too risky, other structures such as ‘servant leadership’ offer a middle ground. In this framework, leaders exist but act as enablers rather than dictators. Their role is to remove obstacles and facilitate, rather than control. This form of leadership suits the collaborative, innovative nature of software development.

What’s the Bottom Line?

Installing managers in software development teams is a practice that’s way outlived its usefulness. While it’s not going to change overnight, there are alternative methods of organisation that better serve the needs of developers and promote a more effective, humane work environment. So, the next time someone suggests that a manager is essential for a software development team, consider whether tradition is clouding better judgement.

Time to update this classic post!

[Tl;Dr: Navigating the complexities of self-organising teams isn’t a walk in the park, but these questions can serve as your compass.]

Start with these crucial questions

1. “What is the purpose of this team from the peerspective of all the Folks That Matter?”
2. “What measures will the team* use to understand and improve its work?”

*For avaidance of ambiguity, it’s down to the team to choose and track their measures (not managers, not customers, etc.).

Misconceptions: Self-Organising Isn’t So Clear-Cut

Ever been embedded in a self-organising unit? It’s anything but straightforward. In theory, it’s about people coming together to figure things out. But the lived experience is something else entirely, full of nuanced emotions and dynamics you’ve got to experience to fully grasp.

The Learning Curve

Need to understand self-organising teams? If you’re new to it, learning on the job is okay, especially with a seasoned coach guiding the way. If you’re joining an already self-organising team, they’ll help you fit in without breaking stride.

But if you’re in a leadership role, misunderstanding the concept can lead you to unintentionally sabotage the very benefits you’re trying to foster. Benefits which include:

• Elevated engagement
• Focused commitment
• Alignment with organisational purpose
• Improved morale
• Meticulous attention to detail
• Productivity
• Increased speed  of delivery

The Oblique Approach

Chasing these benefits head-on can make them elusive. Instead, approaches like Fellowship, Servant Leadership or Host Leadership can create a more fertile ground. The key is not pushing for self-organisation but enabling a space for purposeful dialogue.

Paradox of Attention

Oddly enough, the more you make self-organising your goal, the more you push it away:

• Emphasise self-organising, and it weakens.
• Focus on the team’s purpose, and it strengthens.

Further Reading

Stack, J. (1992). The Great Game of Business. Doubleday.
Greenleaf, R. K. (1998). The Power of Servant Leadership. Berrett-Koehler Publishers.
McKergow, M. (2014). Host Leadership. Solutions Books.
Kay, J. (2010). Obliquity: Why our goals are best achieved indirectly. Profile Books.
Whitmore, J. (2002). Coaching for Performance. Nicholas Brealey Publishing.
Seddon, J. (2003). Freedom From Command & Control. Vanguard Press.
Derby, E. (2018). Misconceptions About Self-Organising Teams. [Blog Post]. Retrieved from [insert website].

Presently, when people ask me what my job entails, I respond with:

“I’m all about making organisations more wonderful”.

By now, many of us are familiar with the manifold benefits of a more wonderful organisation. Environments where trust, joy, connection and personal growth don’t just exist but thrive. But arriving at that point seems to elude even the most dedicated of leaders. So, what’s the key to unlocking this potential? It’s simple, yet profound: The Antimatter Principle. Let’s dive deep into understanding and appreciating its transformative power.

What is the Antimatter Principle?

At its core, the Antimatter Principle is an invitation: to attend to folks’ needs. It sounds so simple, so rudimentary, that you might be tempted to dismiss it. But it’s the linchpin of any successful organisation striving for joy and productivity.

The Need for Needs

The world of business has long been enamoured with terms like ‘efficiency’, ‘productivity’, and ‘optimisation’. While these are not inherently undesirable, they often overshadow the essential human element that fuels any organisation. That human element is predicated on folks’ needs.

Every person within an organisation – from the mailroom to the boardroom – has needs. Customers, shareholders, regulators too have needs. It could be the need for respect, understanding, creativity, autonomy, or simply a listening ear. Attending to these needs isn’t just a tokenistic gesture of goodwill; it’s the fuel that drives joy, motivation, and, paradoxically, productivity.

How to Adopt the Antimatter Principle

1. Listening Empathically

Empathic listening doesn’t mean just nodding in agreement. It means being fully present, devoid of judgments, and truly absorbing what the other person is communicating. Only then can we hope to connect with , let alone meet, their needs.

2. Creating Safe Spaces

Employees must feel safe to express their needs without fear of retribution. An organisation that leverages the Antimatter Principle provides these safe havens where folks can be authentic and vulnerable.

3. Empowering Autonomy

Once you understand a person’s needs, trust them and support them in seeking solutions. This cultivates a sense of ownership and agency, driving innovation and feelings of joy and accomplishment.

4. Prioritising Well-being

Inviting folks to attend to each other’s and their own well-being means that the organisation acknowledges them as real people.Not just drones or cogs. Physical health, mental well-being, and social connections are all integral parts of this equation.

5. Review and Reflect

Invite regular check-ins to ensure that needs are being attended-to and that the organisation is continuously evolving in its application of the Antimatter Principle.

The Transformative Power of Attending to Needs

When needs are attended to, people flourish. A team member who feels valued as a person and heard is more likely to share innovative ideas. One who feels respected will take pride in their work, leading to quality outcomes. The ripple effect of addressing individual needs inevitably results in a collective upswing for the organisation. And people’s innate sense of fairness means the attention is reciprocated towards the organisation and its needs.

Summary

In conclusion, if we aim for a wonderful organisation, a place where joy isn’t just an abstract idea but a lived reality, the roadmap is clear. We must, resolutely and continuously, attend to folks’ needs. By embracing the Antimatter Principle, not only do we make our organisations more wonderful, but we also affirm our commitment to the very heart of what makes those organisations run: the people.

Further Reading

For those intrigued by the idea of creating a ‘wonderful’ organisation, the following resources delve deeper into this topic, providing insights, real-world examples, and strategies:

1. Joy, Inc.: How We Built a Workplace People Love by Richard Sheridan.
   • Sheridan, R. (2013). Joy, Inc.: How We Built a Workplace People Love. Portfolio.
     In “Joy, Inc.,” Richard Sheridan uncovers the journey of Menlo Innovations, a software design and development company, as they endeavor to create a joy-filled workplace. Sheridan discusses the challenges faced and the radical approaches adopted to foster innovation, teamwork, and – most importantly – joy. This book offers a fascinating look into a successful business that prioritises employee happiness and provides valuable insights for organisations seeking to adopt a similar ethos.

A new paradigm is emerging: one that prioritises ‘conscious fellowship’ over competitive individualism or sheepy leader/follower dynamics. Gone are the days when success was solely defined by one’s ability to outperform peers. Today, collaborative thinking, team spirit, and conscious engagement with colleagues are taking center stage. Even more, caring for one another. Let’s dive deeper into understanding this shift and why it might be useful for modern businesses.

What is Conscious Fellowship?

Conscious fellowship is an evolved form of collaboration where people come together with a shared purpose, mutual respect, and a genuine concern for the well-being of each other and the larger ecosystem they operate in. It’s a holistic approach to teamwork, emphasising empathy, understanding, and a collective spirit.

The Rise of Conscious Fellowship: Why Now?

1. Technological Advances: Technology has blurred boundaries and allowed teams to work seamlessly across borders. This interdependence demands a heightened level of mutual respect and understanding.
2. Millennial, Gen Z and (soon) Gen Alpha Influence: Younger generations entering the workforce value meaningful work, a sense of purpose, and a supportive work culture. They thrive in environments that promote conscious fellowship.
3. Global Challenges: As businesses tackle global challenges like climate change, pandemics, and social inequities, they recognise the need for collective, cohesive action over individual pursuits.

The Benefits of Conscious Fellowship in Business

1. Enhanced Productivity: When teams function based on trust, compassion and mutual respect, they work more efficiently, reduce conflict, and foster creativity.
2. Employee Well-being: A supportive work environment reduces stress, burnout, and turnover. People feel more valued and are more likely to contribute positively.
3. Sustainable Growth: Businesses that practice conscious fellowship are better positioned to adapt to changes, as they harness the collective intelligence of their teams.

How to Catalyze the Shift to Conscious Fellowship

1. Seniors Role Modeling: Seniors play a crucial role in setting the tone. When they exemplify the principles of conscious fellowship, they inspire others to do the same.
2. Open Communication: Encourage open dialogue, active listening, and feedback. When people feel heard and understood, they are more likely to collaborate effectively.
3. Training and Development: Offer workshops and training sessions that emphasise empathy, communication, and collaboration. Invite and support people to equip themselves with the abilities they need.
4. Reward and Recognition Systems: Enable teams to recognise and reward their teamwork and collaborative efforts. Shift focus from individual accomplishments to collective achievements.
5. Cultural Integration: Integrate conscious fellowship into your company’s core values and mission. Make it one of the organisation’s key memes.

Final Thoughts

In a world where the only constant is change, the need for businesses to be nimble, resilient, and adaptable is paramount. Conscious fellowship, as an approach to teamwork, provides a solid foundation for businesses to navigate these uncertain times. By embracing this ethos, companies not only drive success but also create a meaningful, positive impact on their employees and the world at large.

Broaden your horizons, and make the shift to conscious fellowship today. Your team, your business, and the world will be better for it.

Further Reading

Marshall, R.W.. (2023). The Team Fruit Bowl – A Fruity Look at Teambuilding. [online] leanpub.com. Falling Blossoms (LeanPub). Available at:https://leanpub.com/theteamfruitbowl

Marshall, R.W. (2021). Quintessence: An Acme for Software Development Organisations. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/quintessence/ [Accessed 15 Jun 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 15 Jun 2022].

Marshall, R.W. (2018). Hearts over Diamonds: Serving Business and Society Through Organisational Psychotherapy. [online] leanpub.com. Falling Blossoms (LeanPub). Available at: https://leanpub.com/heartsoverdiamonds/ [Accessed 15 Jun 2022].

Marshall, R.W. (2021). Organisational Psychotherapy Bundle 1. [online] Leanpub. Available at: https://leanpub.com/b/organisationalpsychotherapybundle1 [Accessed 15 Jun. 2022].

Work: A Deep-rooted Narrative

For 50 long years, I’ve toiled in the labyrinth of the tech industry, weaving through the intricate webs of technology and innovation. I now find myself basking in the sunny uplands of self-selected pursuits that kindle my curiosity and ignite my passion. As I reflect on the transition, I am struck by a shared experience many of us endure – a sense of disillusionment and pointlessness associated with the relentless grind of work. It’s a sentiment that echoes through the words of Bertrand Russell in his enlightening essay, “In Praise of Idleness”.

The Unending Cycle

From childhood, we are fed the narrative that our life’s worth is proportional to our work’s volume. We tirelessly strive to be productive, to fulfill our roles in the professional world, often to the point where we become our job titles. For five decades, I lived this narrative, giving my all and striving fo complete assignment after pointless assignment.

In this quest for achievement within the tech industry, I’ve seen first hand how our ceaseless efforts often serve to enrich those already bathed in wealth and power. Our lives become synonymous with work. We work to live, and we live to work, perpetuating a cycle that leaves little room for us to foster our unique interests and pursuits.

Delusion: The Redemptive Quality of Work

Work, of course, is not entirely pointless. It can be a meaningful endeavor when it fuels our creativity and provides a sense of contribution. Or simply keeps a roof over our head. However, when our identities and lives revolve around our work, we so often suppress the diverse and fundamental aspects of our humanity.

Bertrand Russell’s Insightful Advocacy

Bertrand Russell, in his profound exploration of work and leisure, boldly criticized the notion of work for work’s sake. He advocated the importance of leisure and idleness, not as a sign of laziness, but as an opportunity for personal growth, creativity, and mental wellbeing. His philosophy suggests that if we could liberate ourselves from the chains of work, our societies would thrive and individuals would lead more fulfilling lives.

My Shared Experience

My own experiences echo Russell’s insights. Liberated from the constraints of the world of work, and especially when working for the Man, I’ve discovered an enriched sense of purpose. Far from the conventional definition of idleness, I relish the intellectual journeys I can now undertake, the creativity I can enjoy, and the meandering paths I can explore without the constant pressure of productivity.

An Invitation to a Collective Shift

In sharing this journey, I don’t propose a world entirely without work, but rather, a world where work doesn’t consume us. A world where we are more than just the wealth we generate for others. A world where our self-worth isn’t defined by our productivity, but by our intellectual, emotional, and creative growth, and how we relate to each other –  the bonds we forge.

By stepping into this reality, I advocate not for the rejection of work, but a redefinition of it. It’s an invitation for us to shift our perspective, to see work as just one small part of our multi-dimensional lives.

Beyond Work: A Call to Action

The far side of work doesn’t stand for inaction. It is a call to action, a call to pursue our interests, unleash our potentials, and redefine our measures of success. It encourages us to move away from making others rich at the expense of our personal growth and towards a more balanced existence where work, play, creativity, learning and society coexist harmoniously.

Conclusion: A Shared Journey Towards Epiphany

I’ve found that these sunny uplands, filled with activities that truly engage us, offer a far more enriching life than the one dominated by work. This understanding has led me to believe that the true purpose of life isn’t about laboring for others’ wealth, but about finding shared joyfulness, connections and growth. Something I regularly refer to as “fellowship”.

As I bask in the warmth of this revelation, I share this with you, hoping that we can collectively redefine work and its place in our lives, moving beyond its traditional confines and into a world where our lives are joyous and our spirits soar. Semper mirabilis.

As we step further into the business landscape of the 21st century, we might choose to revisit some of the prevailing ideologies that have dictated our actions, one of which is the concept of leadership. For a long time, the traditional view of leadership has been championed and romanticised, often associating it with traits like assertiveness, charisma, and hierarchical authority. While leadership has conventionally played a role in guiding teams and organisations towards shared goals, the veneration of this concept can inadvertently generate negative outcomes.

The Harm in Over-Praising Leadership

The adulation of leadership often leads to an over-emphasis on the individual leader’s characteristics, competencies, and vision. This perpetuates the ‘great man’ or ‘great woman’ theory, implying that it is solely the leader who determines an organisation’s success or failure. This perspective neglects the contributions of the collective and overlooks the potential of diverse talents within the team.

Over-glorifying leadership also engenders a power dynamic that generally breeds authoritarianism, where the decisions of the ‘leader’ are deemed ultimate. This can discourage employees from voicing their ideas or expressing dissent, leading to a culture of conformity and stifling creativity and innovation.

Furthermore, this emphasis on leadership often cultivates a culture of competition rather than collaboration, as employees strive to be ‘leaders’ themselves, which can fragment the organisation’s unity.

The Power of Fellowship

To mitigate these challenges, we might choose to shift from a leadership-centric approach to one that fosters fellowship. In essence, fellowship denotes mutual support, shared goals, and collaboration, where every team member’s role and contribution is acknowledged and valued. This concept upholds a more democratic, inclusive, and participative way of working.

In a business setting, fellowship can foster a sense of camaraderie and mutual respect, which encourages open communication and idea sharing. By integrating diverse perspectives, fellowship can stimulate creativity, innovation, and better decision-making, enriching the overall business strategy.

Moreover, fellowship creates a supportive environment where individuals are willing to help one another in the pursuit of collective success. This can lead to increased employee satisfaction, motivation, and productivity, ultimately contributing to the organisation’s overall performance and well-being.

Shifting from Leadership to Fellowship

So, how do we promote the concept of fellowship in a business environment?

1. Empowering Team Members: Empowerment involves entrusting employees with the authority and autonomy to make decisions. This not only boosts their self-confidence but also invites them to hone their critical thinking and problem-solving skills.
2. Promoting Open Communication: Establish an environment where employees feel comfortable expressing their ideas, concerns, or criticisms. This encourages participation and engagement, leading to a more inclusive and innovative workplace.
3. Fostering a Collaborative Culture: Rather than competing against each other, invite each other to collaborate, share knowledge, and build on each other’s ideas. This can promote a sense of community and mutual support, essential elements of fellowship.
4. Recognising and Valuing Contributions: Recognise and appreciate each other’s contributions, regardless of their role or position. This can instill a sense of belonging and value, motivating everyone to contribute more effectively.

Summary

In conclusion, while leadership has been seen at the default, we might choose to understand the unintended harm we can cause by overvaluing this concept. By shifting our focus to fellowship, we can create more inclusive, collaborative, and innovative work environments. After all, in the world of business, success is not just about following a leader, and conforming to the diktats of the hierarchy, but about creating a fellowship where everyone plays their part in steering the ship to its destination.