Consulting

Organizations

When the way the company works does not fit on the org chart.

The best plumber on a job answers what the prints leave open. Where the drawings leave a gap and the field needs an answer, he works it out without telling anyone, and nothing fails. Because nothing fails, nobody upstream hears about it, and the next set of drawings leaves the same questions open. The trouble shows up the first job he is not on.

A subcontractor can look reliable because one project manager has known him for twenty years and gets a call returned the same morning. It is also part of the operating system and is almost never written down. When the project manager leaves, the subcontractor starts looking like the problem, and nothing about him has changed.

Endure observed two projects built from the same drawing set by the same general contractor, with several of the same subcontractors, and some details were still built two different ways. What the first project learned reached the second only where someone went looking for it. The reading moves between the whole system and the granular detail, since the detail is often where the system gives itself away.

That informal system holds until the company gets larger. The same decisions take longer as work crosses more hands. The software changes and the folders multiply, and things everyone thought were understood turn out to live mostly in somebody’s head.

Endure starts with the operation as it runs, following work through the people and tools it touches. The useful questions are where the decision got made, and which handoff depended on someone remembering what happened last time.

Part of the work can be documentation: taking what one person does by intuition and putting it on paper, where it becomes repeatable and can be handed on. In some companies the expertise is spread in small pieces across everyone, so no one holds the whole picture. A company can replace one field or office system with another and still carry the same institutional problem into the new software. In other companies the right people and the right tools are already in place, and it is the structure between them that has stopped working.

Diagnosis comes first. Designing the fix can follow, and so can carrying it out. Wherever it stops, the point is to leave the company running more of itself with fewer dependencies. That can require more people in management or fewer.

Built for owners, managers, and prospective buyers who need to understand how work moves through the company, and for anyone standing one up for the first time.

Starting a New Venture

Someone starting a business often knows their trade and knows a great deal has to happen around it before the first invoice, without wanting to work out what, or in what order. Endure assembles that sequence for the state the business will run in: the filings and registrations, the accounts and coverage that have to exist first, and the point at which the attorney, the CPA, the banker, or the insurer has to be in the room. Entity choice and governing documents stay with the attorney and tax elections with the CPA, while the name, identity, and the language the business opens with run through Studio.

When a Company Changes Hands

A change of hands can transfer the formal business without carrying all of what made the work run: the relationships, the sequence, the reasons behind the odd exceptions. A buyer looking at a company cannot see which of those will leave with the seller, and a new owner inherits a company that used to work and finds that it no longer does, without anything on paper to explain the difference. Endure reads how the work runs, writes down what lived in people’s heads, and keeps the outside relationships and the handoffs working through the change. That reading can happen while an owner is preparing to sell, while a buyer is deciding, or after the papers are signed. Valuation, legal, and tax questions stay with the people who answer those.

Inside Organizations

The founder has seen organizations from the inside and out over a decade, from student government organizations to political organizations to built-realm organizations. Over nearly five years in construction, he used and observed successive software systems replacing one another, several in the field and several in the office, and eventually led a rollout himself, sequencing offices in different parts of the country while projects started and finished and working through the overlap between old and new workflows.

What keeps breaking, or has not been built yet?