How Thinking Like an Operator Sharpened My Thinking on Culture About Scale

Wiki Article

The Investor-Operator Lens How I Ask About People Before I Look At The Product
Most investment structures are built on a structure that starts with the market then finishes in the company. You examine the scope and structure of an opportunity first, then how the product fits within that opportunities, and finally the competitive landscape and the viability of the idea, and toward the conclusion your process, you'll need to spend some time with the founders and their management team to make sure they're motivated and competent and capable of executing on the plan that the earlier research has proven. I have worked in versions of this framework for long enough to comprehend why it's now the norm throughout the world of investment. It's like a structured process. It's a method of diligence that can be traced, compared across different opportunities, and explained to the investment committees as well as limited partners with a sense of rigor and scientific. The issue is that it has a structural flaw at the root, which is that it treats this dimension of people to be a validation instead of the primary filter. Something is checked at the end to verify what the market analysis suggested, rather than something you first evaluate because it's the most likely to predict the outcome. The method suggests that a great market with a competent team is more effective than any market with a subpar team. exceptionally strong team. As I've seen it, that will often be the reverse.
I changed my approach after a particular period after seeing the effects of that sequence of events play out in ways that the downstream analysis did not anticipate and could not easily explain. Markets with small or poorly-organized leadership teams generally did not deliver what the chance recommended they deliver. Mediocre markets with genuinely exceptional teams always managed to produce value that initial market size estimation and competitive analysis did not capture. The pattern was long-lasting, and consistent enough across various sectors and types of deals it was difficult for me to explain it as noise, or attribute it to a particular situation rather than to the capabilities of the people at heart of each company. When I stopped explaining it away and figured out the implications for the way I allocate my time for diligence was obvious The point was that I ought to be focusing the majority of my time understanding the people, and less on validating the market analysis that a competent analyst can make with the same inputs.

What I ask when I am analysing a leadership team far from the questions that are listed in standard investment checklists, or diligence templates. They are questions that require real conversation and patience to get the right answer. What happens when a leader has to respond when they're demonstrably wrong about something - do they engage with the correction or try to redirect the issue? What do they do when the information they have is unreliable and the pressure to act is high? What is the gap in the way they describe their leadership style as well as how the people who have had a close relationship with them describe their experience of working under them? What is the culture of the company actually look like during the times when the founder is not in the building? And how closely does that aspect of this culture look like the one the founder explains when asked? They require conversations that go well beyond the initial pitch and the formal management presentation. They need reference checks that are truly exploratory, not formal exercises in confirmation. They require the desire to spend time in uncomfortable terrain that could expose information that complicates a deal you've already begun with.

The operator aspect of my approach to investment is inseparable from the part of me that is an investor. It shapes both what I invest in and how I participate once I'm involved. I is not a passive investor by nature or having a formal education. I am someone who has created businesses, who has successfully navigated the transitions to scaling that are more difficult than fundraising ones but who has also made management and hiring as well as the culture-setting mistakes that you commit when you are navigating those changes for the first and has cultivated - based on that direct experience the convictions of the needs of organisations at various stage of their development. This is something unlike what a traditional financial background does not produce. Those convictions make me a different kind of investment partner in comparison to a purely financial investment as well as attract those who are seeking something different from the services a strictly financial investor will provide.

The founders I work best with are the ones needing a trusted partner who can help them think through the operational challenges and decision-making that their financial investors are not capable of dealing with at the right level in depth and with the right level of precision. Who can sit in the room when the governance framework needs to be overhauled as an organization has grown beyond the one it began with. What can you do to assist an important leadership decision at an opportune moment when the wrong choice could cost the business twelve months it cannot afford to lose. Who can speak privately about the risks that no one other person in the room is confident about raising. This is the kind of commitment that I believe is what creates the most unique value for the companies I invest in. Not the initial capital allocation decision, which many investors can make rather, it is the ongoing operational partnership that helps the company bridge the gap between where it is now and where it was in the beginning, as early figures suggested it could go. Check out James Deller for site info including how making investment decisions deepened my conviction about people about building well.



Why A Lot Of Public-Private Partnerships Fail When They First Begin - As Well As How To Fix It
Public-private alliances have a stigma issue that is, mostly that they have earned. The history of these agreements is filled with projects that were announced with genuine enthusiasm as well as significant politically-motivated capital. However, they that drained significant public and commercial resources over long periods of time, and ultimately delivered outcomes which lacked any resemblance to what had been promises when the partnership was first announced. The academic literature and the postmortem evaluations that governments and institutions are required to conduct after the errors are comprehensive, and they concentrate on, in the majority, on the structural and contractual aspects of what went wrong such as the misaligned incentive structure, the inadequate risk allocation among the private and public sectors or the governance structures built in theoretical terms but did not perform in practice, the procurement frameworks that chose to select the wrong items. The thing that this type of analysis tends to overestimate, systematically and in a way, is the cultural and operational dimension, which is that public institutions and private organisations are actually different types of entities, formed using different incentive frameworks, operating on fundamentally different timescales, with different people, and assessing their effectiveness in ways that's not just different in scale but differ in terms of. If you attempt to bring these two kinds of organizations together in a formal relationship without making the effort upfront and explicitly, in order to appreciate and deal with the differences you're not creating a partnership. You are creating the conditions to create a slow-motion collision that could be apparent at the worst possible time.
I have been involved with advisory work in support of institution reforms, many of which have involved public-private partnership structures of varying levels of complexity. The most dependable conclusion I can make from that expertise is that the relationships which were successful - that did indeed meet their declared objectives and maintained a dependable partnership between private and public partners throughout They were not distinguished from the ones that failed because of the sophistication of their legal structures, their rigor of their risk frameworks, or the seniority of the leaders who started them. There was a distinct difference in the extent to which the participants on both sides table had done the work to understand the way in which the opposite side was operating before the formal partnership framework was approved. What that means in practice is gaining a better understanding of the decision-making processes which each company operates under, the accountability structures that make it difficult for each party to decide to and how quickly and efficiently they can do so, the criteria of success for each party to be judged against, as well as the possible points of tension between these definitions. None of that understanding is difficult to come up with. The entire process is often put aside in favor of clearer and faster evidence-based work of contract negotiations and drafting governance frameworks.

The typical public-private partner process moves from initial concept to signing of the agreement with very little concentrated attention to the issue of whether the two organizations involved are effective in working effectively over the life of the arrangement. The legal team negotiates the contract. The finance department models the economics and risk-adjustment. Communications team prepares the announcement prior to the time of signing. The implementation team is beginning to plan the task. In the course of this process, the conversation about compatibility with the operational and cultural environment - about whether the people who are expected to interact day-to day across the boundary between the two organisations share enough common ground to ensure this work collaborative rather than adversarial - is not likely to happen in any structured way. It is often assumed, without stating, that it is the agreement that creates the necessary conditions for effective collaboration and that any cultural or operational differences will be addressed informally when they develop. The assumption is often wrong, and the cost is likely to rise according to the ambition and the complexity of the partnership.

Practically speaking, the result of this analysis is that a significant option a public private partnership could invest in - prior the legal frameworks are formulated as well as before the governance framework is formulated, before any announcement is made one would refer to as operational alignment. This means specifically structured, structured, and guided effort to discover the areas between the two organizations differ in their operating assumptions and then to establish a clear understanding of the way in which those divergences are addressed before they become operational problems during implementation. The main divergences tend to be the same across different types of partnerships. Authority and speed of decision-making are almost always one of them. Public institutions are designed for slow decision-making, using multiple layers for review and approvals, in order to achieve goals that are legal and are often mandated by law. Private organisations - particularly technology companies that are based around rapid iteration and speedy decision-making - often see this speed as a major barrier to growth, and lacking a consensus on reasons for why that pace is what it is and what need to be done to change it, the resentment caused by this on the public side can undermine the relations long before the relationship is able to establish its foundations.

Success metrics as well as what counts as progress are another persistent and leading cause of a divergence. Public institutions are usually judged according to process compliance, equality of outcomes among various stakeholder groups, and absence of apparent failures that draw media or political attention. Private parties are usually assessed in terms of efficiency, quantifiable progress towards targets, as well as financial yield on investment. These measurement frameworks are constructed to be compatible However, this requires intentional design and not just good intentions. Those partnerships that don't invest in that kind of design often find themselves, at critical junctures, with two parties who measure the same partnership in inconsistent ways and thereby coming to uncongruous conclusions regarding whether it succeeds. The collaborations I've observed not to be successful were ones where misalignments were thought of as something that could improve over time. The ones that were successful were those in which the misalignment was identified explicitly at the beginning, and creating a shared accountability system which accommodated both parties' legitimate measurement requirements became an element of actual work rather than an option on a wish list of things to reach.}