Skip to main content

Art of the Start: Causation

I recently started reading Art of the Start by Guy Kawasaki. Guy was probably one of the first "recognized" technology evangelists and has written lots of books on the topic. Each of his books always seem to be slightly different variations on the same theme - on how to create something that completely changes lives (loosely: Selling the Dream was on how to sell it, How to Drive Your Competition Crazy was on how to compete with it, Rules for Revolutionaries was on creating it) - so I wasn't too sure how his new Art of the Start would read, especially since his new focus is on helping startups get venture capital. But once again, he's really done a good job.
 
The first chapter, Causation identifies what you really need to work on: Meaning, Mantra and MAT (Milestones, Assumptions and Timetables).
 
Instead of all those books that say study this and plan for that, come up with a mission statement and the like, Guy promotes the easier to remember style of a Mantra. Who wants to remember a huge mission statement when a five or six word mantra will do? In fact, one of his first exercises was to write your mantra in the following space: __________________ .  Not a lot of space - but what a GREAT guideline! Now you can actually remember what you do (for all those unclear moments)
 
 

Comments

Popular posts from this blog

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...