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
Planning doesn't make for better software A Fragment by Robin Rendle www.robinrendle.com My own time in a Silicon Valley startup has proved this much to be true; planning doesn’t make for better software. In fact today our design systems team doesn’t have sprints, we don’t have tickets or a daily standup. Each day we come to work, figure out what’s the most important thing that we could be doing, and then we—gasp!—actually do it. Watching so many other teams slowly flail about whilst they plan for quarter 3.2 of subplan A, whilst our team produces more work in a week than they all do combined in a quarter has been shocking to me. After four years of working in a large startup, I know what I always assumed was true: you don’t need a plan to make a beautiful thing. You really don’t. In fact, there’s a point where overplanning can be a signal of inexperience and fear and bullshit. The scrum board and the sprints and the inane meetings each and every day are not how you build another Super Mario 64. Instead all you have to do is hire smart people, trust them to do their best work, and then get the hell out of their way. Why Software is Slow and Shitty planningsoftwareagile