The method Well no, see, that’s the tricky part. I always try to come up with things that when they find out the method, the method is as interesting as the effect itself. — David Blaine Richard Saul Wurman, Understanding Understanding magic
Ancient magicians as innovation consultants An Article by Matt Webb interconnected.org The Codex Justinianus (534 AD), being the book of law for ancient Rome at that time, banned magicians and, in doing so, itemised the types: A haruspex is one who prognosticates from sacrificed animals and their internal organs; a mathematicus, one who reads the course of the stars; a hariolus, a soothsayer, inhaling vapors, as at Delphi; augurs, who read the future by the flight and sound of birds; a vates, an inspired person - prophet; chaldeans and magus are general names for magicians; maleficus means an enchanter or poisoner. I happen to have spent my career in a number of fields that promise to have some kind of claim to supernatural powers: design, innovation, startups… It’s not hard to run through a few archetypes of the people in those worlds, and map them onto types of ancient magician. Those like Steve Jobs (with his famous Reality Distortion Field) who can convincingly tell a story of the future, and by doing so, bring it about by getting others to follow them – prophets. Inhaling the vapours and pronouncing gnomic truths? You’ll find all the thought leaders you want in Delphi, sorry, on LinkedIn. Those with a good intuition about the future who bring it to life with theatre, and putting people in a state of great excitement so they respond – ad planners. Haruspex. Those who have the golden mane of charisma: enchanters. Startup founders. People with a great aptitude for systems and numbers, who can tell by intuition what will happen, from systems that stump the rest of us. We call them analysts now. MBAs. Perhaps the same aptitude drew them to read the stars before? Mathematicus. Steve Jobs: The Lost Interview magicinnovation
Deadlines are bullshit An Article contrariantruth.substack.com In software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil. External vs. internal deadlinesWhy are internal deadlines evil?Engineers who love their work Hofstadter's LawThe Thing-deadline calculusNever enough timeDriving engineers to an arbitrary date is a value destroying mistake bureaucracysoftwareprocesswork
External vs. internal deadlines When are deadlines necessary? Contractual obligations Technical liabilities (e.g., dependency EOL) Compliance, government, investors, and other external stakeholders What do all of these deadlines have in common? They are all important. They are all deadlines that cannot be missed. They are all external. When are deadlines evil? Your manager says you have a deadline Your software development methodology says you have deadlines What do all of these deadlines have in common? None of them are important. They are arbitrary. They are all internal. They are all bullshit.
Why are internal deadlines evil? Estimation: When estimating engineering work a substantial time investment is required by an engineer in order to get an accurate estimate. Misaligned Incentives: There is an incentive to lie and give estimates much longer than the feature is truly expected to take. Low Morale: Deadlines are likely to be missed often. Repeated failure has a cost to the morale of the team. Micromanagement: Deadlines are wielded by middle managers as a whip to harass and annoy engineers working on features. High Stress: When engineers feel the pressure of other stakeholders holding deadlines over their heads it creates an environment of high stress. High Turnover: On teams with high turnover rates the best engineers have an easy time finding new work and leave quickly, the worst engineers have a difficult time finding work and remain. This selects for a lower quality team over time.
Engineers who love their work The resolution is simple. Never have internal deadlines. Operate on a prioritized and ordered list of features. Estimate only when necessary to prioritize and do so in a t-shirt sizing way. Trust your engineers and they will begin to love their work. Engineers who love their work are happy and productive. Building is never a straight line