Skip to main content

Inspirational Ideas from Guy Kawasaki on Starting New Things

I've been reading Guy's new book, Art of the Start for a while now (it's been hard between other projects but I was able to read it on my flight down to NC).

It's a great book for start-ups, filled with Guy's humour and thoughts. If you've read his other stuff, you may find it a little repetitive (he always includes a chapter on how to be a better person - or in this case a Mensch) but I dog-eared a few things that just make it worthwhile. Rather than simply say a page # and tell you to go look it up in the bookstore (yes, Robert, Page 173 talks all about how much every company needs evangelists - not a new concept for Guy), I thought I'd pass on a few quips here.

Pg 73: The worst thing to do is write a "deliberate" plan and then stick to it simply because it is "the plan". Guy notes the difference between a deliberate (which is based on road maps and analysis) and an emergent plan (which is based on reacting to opportunities as they appear).

Pg 96: Bootstrapping a Business - Cost cutting. The enemy of small businesses isn't high spending - it's failing to actually use the spending you currently do, in short, Execution. Dana Epps also mentions it here.

Pg 101: Recruiting - Make the effort to "recruit" your existing employees every day. Make them feel like they WANT to continue working for you, or at least, come back the next day. ("Everyday is a new contract between you and your employer")

Pg 112: The Stanford Shopping Test is an amazing way of testing how you recruit people. If you don't want to "bump" into your employees, prospects, etc in a mall, then don't hire them. Life is too short to work with people you don't like.

Guy's book doesn't just have pages of insight. One of the most valuable pieces of it are the FAQs, where he answers questions that were asked while he was writing it. Everything from forming partnerships, to "getting it" and more.

Guy's big on karma and doing the right thing. And I'll just end the post with his note on patents:

The best protection of an idea is great implementation of the idea.

This book should be on , not just every startup entrepreneur's, but every owners/managers/employee's, desk. Just as Code Complete provided well-thoughtout best practices for programmers, the Art of the Start provides a great guide, not just for startups, but for anyone with an idea who wants to make it last.

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...