Working Theories
Where technology, engineering judgment, and company building are heading, and how to bet on it now.
Resource Hub · since 2003
211 pieces on the problems that actually reach a technology leader: what an architecture review should catch in the first hour, where engineering budgets quietly leak, which compliance work is worth automating, how AI changes who does what on a team, where the CTO role is heading, and why interoperability stalls for organizational rather than technical reasons.
This is the routine, tactical layer of the work, written to be used this week. The books are the longer-form strategic argument that sits on top of it.
Where technology, engineering judgment, and company building are heading, and how to bet on it now.
Patterns captured from building, running, fixing, and funding real companies, ready to apply on Monday.
The comfortable assumptions costing teams money, and what to do once you stop believing them.
What is actually shipping in tech, the CTO role, government modernization, medical devices, pharma, and health IT, reported by someone building it rather than covering it.
For CTOs, founders, and operators deciding what to build, buy, fund, sell, or stop
Alpha, in investing, is the return you cannot explain by the market. Native Alpha is the operating version: the unusual advantage already sitting inside your company, your customers, your data, and your relationships, and the discipline of letting it decide what you build, buy, fund, sell, protect, and stop.
Read the series · 8 pieces →September 10, 2026
Revenue is not the same thing as being alive. A test for founders of mature software companies: if you started this company today, knowing what AI makes possible, would you build anything resembling what you now operate?
September 9, 2026
A guide for executives who think every technical problem should already be obvious to the engineering team. Simple after discovery is not the same thing as obvious before discovery, and confusing the two produces terrible management decisions.
September 9, 2026
The reflex when a business stakeholder derails a technical working session is to stop inviting them. That is almost always the wrong fix. What technical meetings need is rules of engagement, not walls around engineering.
August 30, 2026
Alpha, in investing, is the return you cannot explain by the market. Native Alpha is the business version: the unusual advantage already sitting inside your company, your customers, your data, and your relationships, and the discipline of letting it decide what you build, buy, fund, sell, and stop.
August 30, 2026
For non-trivial changes to legacy systems, define the business outcome first, then how you will prove the change works, before you estimate or build it. Outcome, evaluation, bounded discovery, incremental implementation, in that order.
August 29, 2026
Alpha in finance is the return you cannot explain by the market. Here is what that actually means, why investors bother separating skill from luck, and which parts of the idea carry over to running a company and which do not.
August 28, 2026
AI made building things dramatically cheaper, which quietly destroyed a lot of differentiation that was never real. How to tell commodity execution from differentiated execution, and where to spend the judgment you have left.
August 27, 2026
Enthusiasm inside a company proves nothing. The strength of evidence for an advantage is measured by what somebody outside gave up to act on it, from a compliment at the bottom to a renewal at the top.
August 26, 2026
The same product can be ordinary for one buyer and transformative for another. Product-asymmetry fit and the Ideal Alpha Profile explain why the customer with the biggest problem is often the wrong customer.
August 25, 2026
Advantage is contextual, it hides at surprisingly small scales, it needs protection in the place it actually lives, and it expires. How to find it, where to put the fence, and when to admit it is gone.
Fieldbooks in formation
Some problems keep coming back, so the pieces about them get pulled together and expanded into a single working guide. Two are underway: how an AI-native engineering organization is actually run, and how to make compliance and evidence something machines produce rather than people chase.
Forming · 10 chapters in formation
A Shahid Shah Fieldbook
AI does not make technical judgment cheaper. It makes judgment the scarce input, and it moves the technology executive from best engineer in the room to the person who orchestrates machines, teams, and customers toward outcomes.
See what is going into it →Forming · 8 chapters in formation
A Shahid Shah Fieldbook
Assurance built on human attestation produces documents, not security. The organizations that survive scrutiny are the ones whose systems can prove their own state continuously, by machine, without anyone being asked to vouch for it.
See what is going into it →The Field Archive
Short entries written in the middle of the work: integration problems, tooling decisions, standards fights, early health IT, and whatever I happened to be taking apart that week. Plenty of it still holds. Browsable by year and searchable.
Open the Field Archive →Find it by subject
If you came here with a specific problem, start from the subject.
Oldest entry December 24, 2003