From Praqma to C.R.O.W.D.: The Phoenix Story

This journey is about recognizing that optimization is not enough. We need a new foundation.

The Praqma Era (2003–2023)

For two decades, Praqma pioneered the DevOps revolution. We proved that:

Lean principles could transform software delivery
Continuous Delivery eliminated deployment anxiety
Automation freed humans to focus on meaningful work
Developer experience directly impacts organizational success

Praqma’s mission was simple: “We want to make the world a better place — at least the world of software.”

We succeeded in many ways:

Helped hundreds of organizations adopt lean software practices
Trained thousands of engineers in DevOps principles
Built tools and frameworks that became industry standards
Contributed significantly to open source

But as we evolved, we faced a harder question: Is optimizing the existing system enough?

The Crisis of Sustainability

By 2020, the software industry was experiencing a comprehensive crisis:

Developer burnout was epidemic — even with better tools and practices
Digital waste was accelerating — billions of devices discarded annually
Extractive business models dominated — users treated as products
Technical debt was systemic — unmaintainable legacy systems everywhere
Fragility was increasing — complex systems breaking under stress
Loss of autonomy was spreading — technology controlling rather than empowering

These weren’t problems we could solve with better DevOps tooling. They were problems rooted in how the software industry was fundamentally structured.

As one of our founders said:

“We’ve optimized the machine, but we’ve never questioned whether we should be building this machine in the first place.”

The Think-Tank Emergence

Around the same time, DevOpsDays — the global conference series Praqma helped launch — was becoming a forum for these deeper questions:

What role can technology play in ecological restoration?
How do we build software that serves communities instead of exploiting them?
What would regenerative software engineering look like?
How do we prevent burnout while maintaining integrity?

Participants began asking: Could DevOpsDays evolve into a global think-tank?

Praqma had the credibility. We had a network. We had practical experience. But we were constrained by business model and incentives.

What if we merged?

The Integration: Rise of the Lean C.R.O.W.D

In 2023–2024, we took the leap:

Transitioned Praqma from a traditional consultancy to a non-profit professional business
- We maintained compensation and employment quality
- We eliminated pressure to maximize profit extraction
- We aligned incentives around impact, not revenue growth
Merged the consulting practice with the think-tank
- Consulting projects became case studies for research
- Research informed new consulting methodologies
- Every deliverable contributed to systemic knowledge
Rebranded from “Praqma 2.0” to “Lean C.R.O.W.D.”: Design Science Laboratory
- C — Curious (the think-tank’s analytical approach)
- R — Regenerative (moving beyond sustainability)
- O — Optimize (Lean principles from Praqma)
- W — Whole (systems thinking)
- D — DORITH (Do the Right Thing)
Implemented the Triad Governance Model
- Employees, Client-Members, and Contributors all have democratic voice
- General Assembly makes strategic decisions
- Board provides oversight
- C-level executes the mission
Created the Regenerative SDLC
- Applied DevOps principles not just for speed, but for sustainability
- Integrated participatory design as standard practice
- Measured impact beyond delivery metrics

The Phoenix Metaphor

We chose Phoenix deliberately. In mythology, the Phoenix burns itself completely, only to be reborn stronger.

We’re not abandoning our Praqma legacy. We’re transforming it.

What we kept:

Deep expertise in Lean and DevOps
Proven ability to transform organizations
Credibility in the software industry
Commitment to excellence
Network of global practitioners

What we transformed:

From profit-maximization to impact-maximization
From vendor-customer to member-community
From optimization to regeneration
From “we know best” to participatory design
From isolated consulting to integrated research-practice

The Evolution Continues

We’re in year two of this transformation, and we’re learning rapidly:

What’s working:

The non-profit model attracts mission-driven talent
Client-members deeply engage in long-term transformations
Research informs practice in real-time
The culture shift toward ethical stewardship is palpable

What we’re still learning:

How to scale while maintaining integrity
How to balance research investment with project delivery
How to navigate governance with honest conflicts between stakeholders
How to measure true regeneration, not just reduction of harm

The Larger Vision

The Lean C.R.O.W.D. is not an isolated experiment. We’re part of a larger movement:

Academic institutions rethinking computer science education
Technologists building ethical tools for open-source commons
Organizations transitioning from extractive to regenerative models
Governments regulating platform monopolies
Communities reclaiming agency over technology

Our role is to:

Demonstrate that a regenerative model is viable
Innovate new practices and frameworks
Document our learnings for others to build on
Scale by developing practitioners who multiply our impact
Contribute to the global commons

For Those Joining This Journey

If you’re considering joining the Lean C.R.O.W.D. as an employee, client-member, fellow, or contributor:

You’re joining a young organization still defining itself (which is messy but authentic)
You’re part of a movement, not just a job
You’ll have real voice in strategic direction, not just task execution
You’ll learn regenerative principles that will reshape how you think about technology
You’ll contribute to something larger than yourself

The story from Praqma to C.R.O.W.D. isn’t about rejecting what came before. It’s about evolving it toward something better.

Buckminster Fuller said: “To change something, build a new model that makes the existing model obsolete.”

We’re building that model. In software, it’s possible. And we invite you to help.