Participatory Leadership and Developing a Culture of Psychological Safety
- Aisha Washington
- 4 hours ago
- 7 min read
Psychological safety is often treated as a cultural objective that leaders can establish through policies, workshops, or reassuring statements. In this conversation with InfoQ Engineering Culture Podcast host Shane Hastie, Nick Takava presents a more demanding view: safety emerges from the way people meet, listen, decide, learn, and share power every day.
Drawing on a career that spans early software development, organizational leadership, community work, and participatory practice, Takava argues that healthier teams require more than a new management vocabulary. They need practical structures that let people exercise agency, surface disagreement, and shape the environment in which they work.
From Early Software Development to a Different Kind of Leadership
Takava was born and raised in Zimbabwe before later becoming an Australian citizen. He entered software development in the early 1980s, when formal pathways into the profession were limited. Much of his early education came from experimenting with computers, writing code, and learning through mistakes.
After completing a COBOL programming course, he secured work that exposed him to large software organizations and government projects. His technical experience included older computer systems and languages such as BASIC and Visual Basic. It was an era in which developers frequently had to understand the constraints of both hardware and software at a detailed level.
Technical competence, however, did not automatically prepare him to lead people. When Takava eventually ran a software business and managed a substantial team, he found the human side of the role difficult. Academic exposure to industrial studies and psychology had not given him everything he needed to create a genuinely collaborative workplace.
An unexpected part of his leadership education came through dance. During a retreat with a contemporary dance company, he began developing a deeper capacity to listen and pay attention to how people interact. He was subsequently introduced to the Art of Hosting through Mayan K at Kufunda Learning Village in Zimbabwe. That encounter opened a path toward participatory leadership.
Takava began bringing those practices into his software organization. Although he had not yet encountered Agile as a formal movement, he was already searching for ways to reduce hierarchy, empower developers, and make collaboration part of the operating model rather than an occasional exercise.
Participatory Leadership Redistributes Power
In Takava’s account, participatory leadership begins with how each person enters a shared space. It challenges the industrial model of the organization, in which authority flows downward and a small number of people are expected to think for everyone else.
The alternative is closer to an ecosystem: participants retain their own power while remaining accountable to one another. Cooperation, permission, and mutual recognition replace the assumption that rank alone determines whose judgment matters. Leadership becomes an activity that can move among people according to the situation.
Takava connects this shift with the decolonization of organizations. The idea is not merely to change job titles or remove a layer of management. It means examining inherited conventions embedded in meetings, decision processes, information access, and definitions of expertise. A company may describe itself as flat while still concentrating all consequential choices at the top.
This is especially relevant for engineers moving from individual-contributor roles into management. Their value can no longer be measured primarily by their own output. According to Takava, leadership must encompass the team’s capacity, its internal alignment, and its connection to organizational and customer objectives.
Listening is therefore an operational skill, not a sign of passivity. A leader creates value by helping others contribute their abilities, coordinating collective effort, and knowing when to step aside. Success includes what the work develops in people—not only what the team ships.
Shared Leadership as an Organizational Experiment
Takava describes PAB as a worker-owned cooperative built around shared leadership and conscious, courageous, creative collaboration. Rather than presenting its model as a finished blueprint, the organization treats governance as an ongoing experiment.
That experimental stance matters because participatory leadership cannot simply be installed as a generic framework. Teams need enough structure to coordinate effectively, while retaining the ability to adapt practices to their own context.
Takava’s work also extends into entrepreneurship and Australia’s multicultural community, including support for African Australian entrepreneurs. This broader involvement reinforces a recurring theme in the conversation: organizational design is inseparable from questions of belonging, access, and whose knowledge is taken seriously.
Micropractices Turn Principles into Daily Behavior
Large cultural aspirations become credible only when people can enact them. Takava discusses a collection of accessible micropractices informed by the seven domains in Samantha Slade’s book Going Horizontal. These domains are not offered as scientific classifications. They are lenses through which teams can examine autonomy, purpose, meetings, transparency, decisions, learning, and relationships.
Autonomy starts with claiming personal leadership. It does not mean acting without regard for others; it means recognizing one’s responsibility and capacity to contribute. Clear purpose then provides a shared reference point. When people understand why the work, product, and relationships matter, purpose can guide action without requiring constant managerial intervention.
Meetings provide a practical test of these commitments. In a co-managed meeting, participants can propose topics and facilitate the relevant portion of the discussion. Hosting is no longer reserved for the most senior person. This distributes responsibility while giving people direct experience of leadership.
Transparency supports that autonomy. Takava favors openness as the default because people cannot participate meaningfully when important context is withheld. Access to information reduces unnecessary dependency and makes decisions easier to understand.
For decision-making, he describes a generative, consent-based process guided by two pragmatic questions: Is the proposal sufficient for the present moment, and is it safe to test? The aim is not universal enthusiasm or a theoretically perfect answer. It is to move forward responsibly, learn from evidence, and revise the decision when conditions change.
Together, these practices offer a workable middle ground between command-and-control management and unstructured consensus. Participation does not eliminate coordination. It redesigns coordination so that authority and learning are more broadly distributed.
Psychological Safety Is Built in Small Moments
Takava rejects the idea that executives can announce psychological safety into existence. People decide whether a workplace is safe by observing what happens when someone admits uncertainty, questions a decision, asks for help, or proposes an unconventional idea.
Simple check-ins and check-outs can help teams notice the human realities surrounding their work. Used sincerely, these rituals make room for concerns that might otherwise remain invisible and allow groups to monitor their collective health. Their value does not come from the format alone, however. Leaders must respond constructively to what people reveal.
This is why psychological safety and authority are closely connected. Employees often remain silent because they believe they lack permission to change anything. Others protect themselves by withholding incomplete ideas or difficult knowledge. A workplace may invite feedback while repeatedly signaling that vulnerability carries a penalty.
A safer culture expands the range of discussable subjects. Takava points to PAB’s conversations about a conscious economy, including unconventional approaches to salaries and project work. Whether another organization adopts the same ideas is less important than whether its people can examine sensitive arrangements without fear.
Takava also cautions that organizations usually occupy a transitional space. Traditional hierarchy may coexist with newer participatory practices, creating uncertainty about who can decide what. Change therefore requires both unlearning inherited habits and recovering more relational ways of working.
External facilitators or leaders can help build the initial capacity, but their ultimate task is to become less necessary. A participatory culture matures when its members can choose, adapt, and sustain their own practices.
Make Learning Part of the Work
Another central argument is that learning should not be isolated from delivery. Work itself produces the situations through which people develop judgment, relationships, and technical capability.
Takava advocates self-directed learning held within a collective context. Individuals can own their development while making their goals visible enough for colleagues to offer support. Teams benefit when members know what others are exploring, where they need assistance, and how their learning connects with shared priorities.
This approach also changes how conflict is understood. Disagreement does not automatically indicate dysfunction. When people have a clear purpose, transparent information, and trusted ways to work through tension, conflict can expose assumptions and improve decisions. Psychological safety is not permanent comfort; it is confidence that difficult participation is possible.
Inner Development Shapes Outer Results
The conversation also considers the Inner Development Goals movement, which organizes human capabilities into five broad areas: being, thinking, relating, collaborating, and acting. Takava sees these inner dimensions as relevant well beyond formal development work.
Who people are—and how they behave under pressure—affects the products they build. A technically successful system can still emerge from an unhealthy team or cause harm outside the organization. Inner and outer outcomes should therefore be considered together.
This perspective invites leaders to expand their metrics. Delivery speed, revenue, and output remain useful, but they do not describe the whole system. Takava suggests questions such as whether people would willingly work with the same team again. Such a measure reveals something about trust, sustainability, and the quality of collaboration that conventional productivity statistics can miss.
Software Engineering Needs a Broader Definition of Value
Takava closes by emphasizing the unusually influential position of software professionals. Digital products shape decisions, relationships, institutions, and access to opportunity. As artificial intelligence becomes more deeply embedded in daily life, the consequences of design choices will spread further.
For that reason, he argues that engineering’s definition of value should include people, planetary impact, wellbeing, and communities that are often marginalized. Customer benefit matters, but it cannot be the only ethical boundary. Teams must also ask who is excluded, who bears the risk, and what kind of future their products help create.
Participatory leadership supports this broader responsibility because it brings more perspectives into the work. Psychological safety makes it possible for people to raise ethical concerns before they become expensive failures—or invisible harms.
The conversation ultimately returns to a simple priority: people make the difference. Developers, customers, colleagues, and affected communities are not secondary considerations surrounding the “real” work. They are the reason the work has value at all.
