In both professional and personal settings, there’s a growing understanding of the critical role communities play in our lives. The next step after buying into this premise is to start exploring how once can be more intentional in shaping those communities and monitoring their health. Similar to culture, while there are no good ones and bad ones, there are strong ones and weak ones. What sets the former from the latter is the degree to which the various elements that shape a community are defined and in alignment with one another. While much has been said and written on the topic, none competes in clarity and comprehensiveness with the work Fabian Pfortmüller, Nico Luchsinger, and Sascha Mombartz did in creating the
The Community Canvas is a framework for creating, analyzing and improving communities. It lays out all the elements that define a community in a coherent canvas format.
The canvas is divided into three main sections, each in-turn is broken down into more specific themes:
Section 1: Identity — who are we and what do we believe in?
Purpose — Why does the community exist?
Member Identity — Who is the community for?
Values — What is important to us as a community?
Success Definition — How does the community define success?
Brand — How does the community express itself?
Section 2: Experience — what happens in the community and how does it create value for the members?
Selection — How do people join the community?
Transition — How do members leave the community?
Shared Experiences — What experiences do members share?
Rituals — What rituals happen regularly?
Content — What content creates value for members?
Rules — What are the community’s rules?
Roles — What roles can members play?
Section 3: what gives us stability in the long-term?
Organization — Who runs the community?
Governance — How are decisions made in the community?
Financing — What is the community’s plan to be financially sustainable?
Channels & Platforms — What channels does the community use to communicate and gather?
Data Management — How does the community manage the data of its members?
Thinking about a particular community that you are part of, makes it easy to see the framework’s strength (and minor weakness) — Themes with clear and well-defined answers are areas in which the community is strong. Themes with no-so-clear answers, present opportunities for strengthening the community. My one nit of the framework is that while it’s fairly comprehensive, it’s not perfectly MECE some themes seem to have some overlap between them so there’s a structural opportunity to eliminate this overlap and likely simplify the framework a bit in the process.
Juho Makkonen is the founder and CEO of a Finnish company called Sharetribe and his unique perspective first came across my radar in a more recent post he’s written about shifting the licensing for Sharetribe’s product from “open-source” to “source available” (Specifically, from MIT to Sharetribe Community Public Licence), closing a big, exploitative loophole in the standard open-source license by preventing organizations that utilize their code to use it in a product that competes with the company who made the code available in the first place. For example, if you’ve built a web browser and made its source code available, under an “open source” license another company can just take that code and build a competing browser with it, while under a “source available” license, it can’t.
Smart. Thoughtful. Progressive. The kind of impression that often leads me to an “I wonder what else they’ve written about” inquiry. And I was up for a big, pleasant surprise.
You see, a year ago, Jujo wrote a profound piece called
In the post, Juho outlines how he restructured the governance structure of Shaerscribe to ensure that the company stays true to its purpose and not succumb to the pervasive profit and shareholder value maximization paradigm.
The new structure consists of 4 key pieces:
1. For-purpose corporation
In most countries, the default articles of incorporation require the management team of an organization to use the maximization of shareholders’ profit as the north star in corporate decision making. Failure to do so can make managers liable to a lawsuit for violating their fiduciary duty. Sharescibe made an explicit change to their corporate bylaws overriding the default with the following: “The purpose of the company is to democratize the sharing economy. The company aims to foster an economy where resources are utilized efficiently, created value is distributed fairly, and people have control over the conditions of their work.” So in cases where there’s a conflict between making a profit and pursuing this purpose, management is not legally bound to abandon the latter for the former.
Furthermore, acknowledging that the purpose, as it is defined today may evolve over time, Sharescribe created the option of changing the company’s official purpose as long as the people owning two-thirds of the company’s voting shares support it (with an important caveat we’ll cover in part 4).
This governance piece is not too novel in and of itself. It is very similar to other progressive governance structures like Public Benefit Corporations that also eliminate shareholder primacy. But it gets more interesting when tied with the other pieces.
2. Employee ownership (voting rights)
Sharetribe aims to be in control of the people who hold active roles in it. Namely, its employees. Therefore it is governed by the people working in it, guaranteeing that the management of the company will be in the best interests of employees and all other stakeholders. At Sharetribe this is done by issuing 4 types of shares:
Class A — voting rights shares (not entitled to a share of the profit) — available only to employees and people in a service relationship with the company. Must be sold back to the company at a nominal cost if the relationship is terminated.
Class B — a single veto vote share granted to a foundation (see part 4)
Class C — profit-sharing shares (no voting rights) — given to investors (see part 3)
Class D — profit-sharing shares (no voting rights) — given to employees (see part 3)
3. Reliable returns — Redeemable shares for investors and employees (no bonuses, no dividends)
To avoid the “go big or go home” financial returns pressure that’s inherent in the standard VC model, Sharetribe opted for a different funding model:
Sharetribe offered its investors to buy (Class C) shares at the company at 20 Euros a piece. In return, the company commits 40% of its annual profit to redeem these shares at 100 Euros a piece (x5 return) until they have been fully redeemed. If the shares are not redeemed within 10 years, 100% of the company’s annual profit will be directed towards redeeming the outstanding shares. Sharetribe currently estimates that they’ll be able to redeem all outstanding shares within 7–8 years.
Juho walks through the economic business case for investors in using such structure which essentially boils down to the lower per-company return being offset by the lower failure rate, yielding the same average returns as a high-returns high-failure-rate portfolio.
In many ways, this is similar to the funding and investment strategy pioneered by indie.vc in the US.
However, Sharetribe also opted to extend this model even further, and use the same vehicle with its employees as well, granting them Class D shares rather than the typical ISOs or RSUs since the liquidity event that such vehicles depend on (IPO, acquisition) is no longer possible. The Class D redemption schedule is designed in a way that most of it take place after the Class C shares have been fully redeemed. It’s not fully clear whether this mechanism is meant to be a permanent part of the compensation scheme, or just be a “one-time” fix to compensate the founders and early employees for accepting below-market wages in the early days of the company. If it’s the former, transitioning to a profit-sharing scheme like the one outlined here may be in order.
4. Safeguarding the structure — veto shares held by a foundation
The final piece in the puzzle is ensuring that the transition to steward ownership is permanent. History has shown that changes in management can pose a risk to maintaining the steward ownership governance structure and open the door for reverting back to a more conventional governance mode.
To address that risk, Sharetribe granted a (Class B) veto voting share to a foundation with no economic stake in the company. This veto share can only be used to veto any change in the company’s articles of association that would attempt to dismantle the steward-ownership structure. The foundation is bound by its rules to veto any such change, and whoever is on the board of the foundation must respect these unchangeable rules.
Stepping back, it’s easier to see how these four pieces fit together.
While no governance scheme offers full immunity to the “human condition” in addressing challenges such as negligence, illegal activity (corruption, bribery), etc. the steward-ownership implementation outlined above seems to masterfully address some of the more systemic issues with conventional capitalism governance structures.
I’ve been thinking about mindsets a lot in recent weeks, as last week’s post about culture may suggest. In the process, I re-read my Pfeffer piece about changing mental models, which rings true today as it did when I wrote it 2.5 years ago and most likely as when the original was written 14 years ago.
Pfeffer wraps up with the following quote (emphasis mine):
In addition to being concerned with the company culture, human resources must be concerned with the mental models and mind-sets of the people in the company, particularly its leaders. Because what we do comes from what and how we think, intervening to uncover and affect mental models may be the most important and high-leverage activity HR can perform.
But Pfeffer left a big question unanswered: how?
Keller & Schaninger, first make a similar case in their own words: mindset is the root cause which causes smart, hard-working, and well-intentioned employees to continue to behave as before, despite the effort and intention to change their behavior. The only way to drive effective behavior change is by reframing the root cause: changing the underlying mindset. From “hoarding information is the best way to magnify power” to “sharing information is the best way to magnify power”, for example.
Then, they pick up where Pfeffer left off, offering a 2-part approach:
Changing mindsets using a U-process offsite
Keller & Schaninger argue that the most effective intervention to get leaders and employees to commit to changing themselves is a 2-day offsite for a small group of 20–30 employees at a time, facilitating a workshop-based learning journey for each of the participants.
The methodology is based on Scharmer’s U-process consisting of three phases:
Sensing. This typically involves a senior leader who has already been through the workshop and shares the company’s change story, describes her or his own personal change journey, and answers questions from participants.
Presencing. This involves participants exploring their personal “iceberg” of behavior. It includes working through modular, discussion-based content and questions that equip leaders to achieve new levels of self-awareness and self-control. “Where and why do I act out of fear rather than hope? Scarcity rather than abundance? Victimhood rather than mastery? And what would be the result if I made different choices?”
Realizing. In this phase, participants make explicit, public choices about personal mind-sets and behavioral shifts; identify “sustaining practices” that will help them act on their insights; and reflect on how they will engage their personal networks for the challenges and support they will need during the rest of their personal change journey.
The offsite is followed-up by small team gatherings aimed at offering peer accountability and advice. And a facilitated session a few weeks out to take stock changes in behavior and determine next-actions.
Reshaping the work environment using the “influence model”
Keller & Schaninger observe a similar phenomenon to the one I outlined last week in which behavior is mutually shaped by both our internal mindsets and the external work environment. They offer McKinsey’s “Influence Model” as a roadmap for reshaping the work environment in a way that’s conducive to the desired behavior change:
Changes in thinking and behaving will be significant and sustained if leaders and employees see clear communications and rituals (the understanding and conviction lever); if supporting incentives, structures, processes, and systems are in place (the formal-mechanisms lever); if training and development opportunities are combined with sound talent decisions (the confidence and skills lever); and if senior leaders and influence leaders allow others to take their cues from the leaders’ own behavior (the role-modeling lever)
Super cool. And kind of looking forward to trying it out in real-life.
It is rather surprising that I managed to get away with publishing this blog for more than 5 years now while never providing my own definition of culture. I’ve shared Laloux/Wilber’s definition of culture, Horowitz’s, and I’m sure I’ve touched upon it indirectly in countless other posts but never explicitly spelled out mine.
I’ve formulated, or perhaps more accurately, synthesized, my own definition about three years ago. But only recently, when responding to a different post on this topic, I realized that I haven’t shared it outside of the organization I was part of at the time (AltSchool).
So here goes. It is influenced mostly by the Laloux definition, and Schein’s (which likely influenced Horowitz’s as well) and consists of three interacting elements:
“Culture is our shared set of beliefs and mindsets, reflected through our behaviors and supported by our organizational systems (processes, protocols, etc.)”
At the end of the day, culture is epitomized in the way we behave. However, our behavior is shaped by an internal source, our beliefs and mindsets, and an external source, the organizational systems in which we operate. It is important to note that the relationship between these elements is not as one-directional as I make it sound, and there are secondary effects through which organizational systems shape beliefs and mindsets, for example.
There are no “good cultures” and “bad cultures”. Every culture has its use and may be optimal to a certain group of people aiming to accomplish a certain purpose together. What sets apart strong cultures from weak cultures is the degree to which these elements are honest, clear and in alignment/congruence with one another.
One of the most common mistakes that organizations make is focusing on defining the first element, beliefs and mindsets, often referred to as values or principles and ignoring the other two. It’s definitely a mistake that I’ve made as well. I’ve written extensively about a process for formulating values or core principles, and I’ll be the first to admit that it muddies the water a bit in distinguishing between the elements, since it was written before I developed this definition. Yet if we look at the 10 core principles that most organizations tend to converge on a subset of, once you peel off the marketing-speak, it becomes a little easier to see why values or principles are not enough.
Mission-orientation, customer focus, risk-taking/creativity, ownership, transparency, humility/learning, simplicity, excellence, tenacity/grit, and speed are not things that have a clear, descriptive and observable definition. This creates a lot of room for misinterpretation and as a result, misalignment, in both directions: when I’m taking these principles and translate them to the behaviors that I believe reflect them, and when others see my behaviors and translate them to the underlying principles that they believe I may hold.
In addition, our formal and informal organizational systems, processes such as hiring, firing, promoting, etc. and practices such as the way we run meetings or make decisions, explicitly and implicitly define a set of behaviors that are encouraged/discouraged. Without careful design, those behaviors may or may not be aligned with the behaviors and, in turn, beliefs and mindsets that we want to encourage/discourage. So let’s put in the extra effort to make sure that they do.
Lectica’s overall approach to learning in a complex world deserves its own dedicated post, which I hope to write one day. Today, I want to focus on a smaller piece of their overall thesis — their framework for “how we learn?” because it stands on its own and is more broadly applicable, regardless of the learning goal that you’re applying it towards.
I am mostly synthesizing content from two sources:
Lectica’s framework, called the “Virtuous Cycle of Learning” or VCoL for short consists of 4 key steps: setting a learning goal → gathering information → applying what you’ve learned → reflecting on the outcome. Sparing you my rant on the overall underappreciated importance of reflection in many other approaches to learning, this macro cycle is very similar to other progressive frameworks describing a learning process, with minor variations in the labeling of the different steps.
When things start to get interesting, and have certainly expanded my knowledge of learning, is in the way Lectica decomposed this cycle further and in the way it is applied to real-world situations.
The +7 skills
Lectica identified 7 key skills that support the practice of learning. Each, in turn, can be strengthened through a set of specific practices.
Awareness of self, others, and the environment: observing and documenting thoughts, feelings, or behavior; self-evaluation; practicing non-judgmental openness to experience; meditation; mindfulness in everyday life; somatic practices, like yoga; coherence practices, like HeartMath
Skills for making connections between ideas, information, emotions, perspectives, and evidence: brainstorming; Minto Pyramid problem solving; polarity thinking (or both / and thinking); mind mapping; causal loop diagramming (or other systems mapping approaches); building relational databases
Skills for seeking and evaluating information, evidence, and perspectives: active listening; deep listening (Kramer); seeking clarification; “library” research; critical thinking; action inquiry (particularly second-person action inquiry); the scientific method
Skills for applying what we know in real-world contexts: action learning; project-based learning; developing action plans or development plans; rehearsing — reducing risk by trying out new knowledge in hypothetical situations; writing or critical discourse — using new knowledge to improve an argument or message
Reflectivity — a cultivated habit of reflecting on outcomes, information, emotions, or events: making sure that learning goals are “just right”; embedding learning in real life, as a part of everyday activities; not punishing learners for making mistakes — helping them see mistakes as a source of useful information; ensuring that every learning cycle, no matter how small, ends with goal setting
Skills for seeking and making use of feedback: openness to feedback; awareness of your own defensiveness; feedback-seeking skills (like helping others feel comfortable providing you with feedback); skills for evaluating and incorporating feedback; second-person action inquiry; participation in focus groups; customer or employee surveys
Awareness of cognitive and behavioral biases and skills for avoiding them: cultivating humility — recognizing the ubiquity of human fallibility; building critical thinking skills; regularly seeking feedback; tackling common cognitive biases, one at a time (e.g., conservation bias, bandwagon effect, stereotyping, or attribution bias)
The 7 skills are also very helpful in better triangulating where the learning cycle is weakest (or breaks down altogether) and then taking focused action to strengthen that particular skill.
Often times we want to work on a macro skill that’s a bit too lofty, abstract or risky to pursue as a whole. Let’s say we want to improve our “collaborative capacity”, for example. It seems like a worthy goal, but where do we begin?
We begin by decomposing the macro skill into something more tangible. For example: part of a strong collaborative capacity is having strong facilitation skills. Facilitation skills, in turn, include but are not limited to having strong active listening skills. Active listening skills can be decomposed to: identifying opportunities for listening, giving others opportunities to speak, etc.
Now we have something in hand that we can more easily run a VCoL around and practice “in the real world” with one additional useful distinction. If we zoom back out to the crude VCoL loop: set, seek, apply, reflect — two stages in the loop, “reflect” and “seek”, are more internal, or done in consultation with a trusted coach or mentor. The other two, “seek” and “apply” is where we engage with the outside environment differently, with the learning goal in mind. And those too can be broken down into micro-VCoLs: an “awareness VCoL”, in which we either increase awareness of opportunities to practice a skill or identify individuals who are proficient in a given skill; and a “practice VCoL”, in which we build virtuosity in the particular learning goal. Examples of the two are shown below.
The next time you set a learning goal for yourself, consider using VCoL as your framework for learning.
Another fantastic piece by Manuel Küblböck whose excellent work I’ve already showcased here. This time, the focus is on how decisions get made at Gini. While the majority of the post covers the mechanics of the various decision-making formats, that was the least interesting part to me, since I’ve already covered most of them, for the most part, in previous posts. What was most interesting, was how the system is structured and the following attributes in particular:
I’m not 100% sure where the 7-levels of delegations model originated from, but I first came across it a few years back on the Mgmt3.0 website so I will give them the credit for now.
This fuller spectrum is being used to anchor the decision-making formats that are actually being used:
Again, while the mechanics of “safe-to-fail/mandate”, “group consent” and the “advice process” are outlined in the post, those are fairly standard formats of decision-making.
This was new and exciting for me. Thinking about the process of choosing the right decision-making format more like a simple, lightweight decision-tree/escalation path with increasing levels of severity:
Is this safe-to-fail? → Do I have an explicit mandate as part of one of my roles to make this decision? → Can the group reach consent (not consensus) about this? → Advice process.
Specifically, thinking about the “advice process”, which is the most lengthy process of the three, as an escalation lever when the group fails to reach consent is very clever and avoids over-using this heavy process. Another interesting aspect here is seeing the escalation arc moving from the individual, to the group and back to the individual, which seems a bit counter-intuitive at first but makes a tonne of sense once you think about it.
This is another cool innovation. Defining a desired, healthy, usage distribution across the different decision-making formats. Heavily favoring and relying upon autonomous/distributed decision-making, using consent-based decision-making only when necessary, and thinking about the advice process as the exception rather than the rule. While the 90%/9%/1% should be thought of more as illustrative, order-of-magnitude guidelines rather than exact percentages, they create a healthy benchmark that can be used to trigger and support troubleshooting when the actual distribution looks significantly different.
Not a new point but one worth emphasizing, since many, myself included, often make this mistake. When we compare the speed of various decision-making formats, we tend to compare the time it takes to reach a decision. But this is the wrong benchmark since decisions are just a means for informing a desired behavior change. So if we want to make a fair comparison on speed we need to look at “time to make a decision” + “time to change behavior” which is beautifully illustrated in this parting image:
I’ll be the first to admit that there’s nothing ground-breaking in this operating rhythm. Some may even say that it’s rather conservative/traditional. But I’ve seen almost identical rhythms, same “building blocks” slightly different cadences, emerge “the hard way” in multiple companies so hopefully, this can save up some and help avoid some “old mistakes” by serving as a starting point to iterate on.
Matt’s post includes more detailed explanations on what each building block entails, as well as some of the nuances around using them that’s specific to Skillshare.
The only thing that the post was really missing is a simple visual to see how all the different pieces of the puzzle fit together across the 4 cadences, so I went ahead and created one at the top of this post.