> ## Content Index > Fetch the complete content index at: https://meridian.ghost.preview.themeanax.com/llms.txt > Use this file to discover other available public pages before exploring further. # Private Markets and the Liquidity Question No Trustee Wants to Ask - URL: https://meridian.ghost.preview.themeanax.com/private-markets-and-the-liquidity-question-no-trustee-wants-to-ask/ - Published: 2026-08-13T09:26:16.000Z - Updated: 2026-09-08T10:35:08.000Z - Description: We spent a quarter trying to get business right, and the useful lessons were not the ones we expected. - Author: Meridian - Tags: #themeseed, Business, Field guide Most teams arrive at business the same way: something breaks, and the fix becomes a habit. ## The one people skip Feedback loops shorter than the planning cycle change everything. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. Try writing the constraint on one line before opening a vendor comparison; the line is usually harder than the comparison. ![a close up of a typewriter with a paper that reads private equity](https://meridian.ghost.preview.themeanax.com/content/images/2026/09/photo-1652957109547-3738f4ce594d.jpg) Photo by Markus Winkler on Unsplash Documentation is a symptom: you write it where the design is unclear. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. The first thing to establish is what you are actually optimising for. The stated constraint is usually a proxy for a real one nobody wants to say aloud, and optimising the proxy is wasted effort. ## The habit that compounds Most of the difficulty lives at the boundaries, not in the middle. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. The caveat is that all of this assumes the underlying goal is settled, which is frequently the actual problem. ![person wearing suit reading business newspaper](https://meridian.ghost.preview.themeanax.com/content/images/2026/09/photo-1444653614773-995cb1ef9efa.jpg) ![brown pencil](https://meridian.ghost.preview.themeanax.com/content/images/2026/09/photo-1542621323-be453184db76.jpg) ![Two hands exchanging a business card](https://meridian.ghost.preview.themeanax.com/content/images/2026/09/photo-1777652918682-dec5c79d1301.jpg) Business in practice The second-order effects arrive about a quarter after the first-order ones. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Set a date at which you will stop, and write down in advance what would make you stop earlier. The interesting constraint is almost never the one in the brief. If you learn on Friday what you assumed on Monday, the assumption never has time to become an architecture. The counter-argument deserves a hearing, and it is stronger than its usual proponents make it sound. ## The advice worth ignoring The expensive mistakes here are rarely the technical ones. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. It helps to separate the decision from the execution. Most disagreements that present as strategic turn out, on inspection, to be two people using one word for two things. The default answer is right often enough to be dangerous. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. Ask what would have to be true for the opposite approach to be correct, and see whether anyone can answer. ## Where to start on Monday The compounding effects matter far more than the individual wins. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. Scope is the variable everyone adjusts last and should adjust first. A small improvement applied consistently beats a dramatic one applied once, which is unsatisfying advice precisely because it is correct. Consider the failure mode rather than the success case. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. In practice the answer showed up in the calendar before it showed up in the dashboard. > Simplicity is not the absence of work. It is the result of it. — Overheard in a retrospective ## The quiet win Measurement is usually where this falls apart. Cutting scope early is cheap and slightly embarrassing; cutting it late is expensive and deeply embarrassing. The version of this that works fits on an index card. The version that fails needs an onboarding session. Consistency is worth more than any individual improvement to business. The first quarter shows the intended effect; the second shows what the intended effect displaced. Reasonable people land elsewhere on this, usually because their constraints differ more than the vocabulary suggests. ## Begin with the obvious one What looks like a process problem is frequently an ownership problem. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. A useful test: if this disappeared tomorrow, how long before anyone noticed? Speed and reversibility are the trade-off worth naming out loud. Being right sixty per cent of the time builds exactly the kind of confidence that makes the other forty per cent expensive. Nobody gets credit for the work that did not need doing. Business rewards clarity here more than almost anywhere else, because the wrong target produces work that looks productive and moves nothing. A few things worth checking before you commit: 1. Name one person accountable — not a group 2. Agree on what "done" means, in writing, before starting 3. Prefer the reversible option when the evidence is thin 4. Write the constraint down before choosing a tool ## What to do first A shared definition of "done" removes more friction than any tool. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. That said, none of this generalises cleanly across team sizes. The tooling question is downstream of the constraint question. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. When we mapped it out, four of the seven steps existed only to compensate for the second one. ## The expensive mistake There is a version of business that is mostly ritual. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. The evidence here is thinner than anyone quoting it tends to admit. Consider the failure mode rather than the success case. The decision is usually cheap and reversible; the execution is where the cost lives, and that is where the argument should have happened. ## The one that only matters at scale The default answer is right often enough to be dangerous. Choosing infrastructure before agreeing what it is for is how organisations end up maintaining a system nobody wanted. The clearest signal was that people stopped asking where things were. There is a version of business that is mostly ritual. It is comfortable, it is legible to management, and it is close to worthless once you measure what it actually changes. Speed and reversibility are the trade-off worth naming out loud. They are decisions made quickly, defended slowly, and built upon for six months before anyone recalculates. ## The one people skip The second-order effects arrive about a quarter after the first-order ones. Where a design is obvious the prose is short, so the length of an explanation is a reasonable proxy for where to look next. The tooling question is downstream of the constraint question. Subtraction is structurally underrated: the meeting that stopped happening leaves no artefact to point at in a review. One team we spoke to cut their review stage entirely and found throughput unchanged, which told them something the metrics had not. ## The habit that compounds The expensive mistakes here are rarely the technical ones. Teams that pick both end up with neither, and usually discover this at the point where reversing would have mattered. The clearest signal was that people stopped asking where things were. Feedback loops shorter than the planning cycle change everything. When responsibility is spread across a group, the work that falls between the named parts is the work that does not happen. The first thing to establish is what you are actually optimising for. The things that are easy to count are rarely the things that matter, and once a number reaches a dashboard it starts shaping behaviour whether or not it deserves to. A useful test: if this disappeared tomorrow, how long before anyone noticed? ## The advice worth ignoring It helps to separate the decision from the execution. Success has many causes and teaches very little; failure tends to have one, and it is usually obvious in hindsight. We ran both approaches in parallel for six weeks. The difference was smaller than the cost of the debate about it. The compounding effects matter far more than the individual wins. Handoffs between people who each hold a coherent local picture and no shared one produce most of the pain later attributed to tooling. This is easier to write than to hold to when a deadline appears. ## Where to start on Monday Documentation is a symptom: you write it where the design is unclear. A team that changes approach every quarter pays a coordination tax that routinely exceeds whatever the change was meant to fix. We will revisit this once we have another two quarters of data. The current answer feels right, which is exactly when it is worth checking.