Shel Israel, co-author of Naked Conversations, currently working on his Global Neighbo(u)rhoods project, is conducting a survey for SAP. I've answered some of his questions from this survey that he's posted on LinkedIN. Recently, Shel has invited the world to "roll their own" and participate in his survey on their on own blogs. Here's my take.
Last night, Clarise and I attended The Brenner Group's 20th Annual Networking Event. Their theme was then and now, celebrating the changes in technology that they've seen come out of the Silicon Valley over their remarkable 20 years of doing business, since Rich Brenner started the firm. Displays around the hall showed the 1984 Mac with the latest black MacBook laptop, an early PDA [poor Palm, not even mentioned by name] with a RIM Blackberry [which is such a pale imitation of the Palm as to be essentially useless - don't get me started], a portable CD player with an iPod, and, well, you get the picture. Door prizes from the various partner-firms/sponsors were things like a CD and an iTunes gift certificate, CDs and an iPod shuffle, and one particularly telling and generous gift of an 8-inch, portable black-and-white television with a modern 15-inch HiDef LCD television.
In very many ways, this was the best party, oops, networking event
that they've thrown in the seven years that we've been attending. It was marred by the absence of our favorite member of The Brenner Group, but he knows that our thoughts are with him. We met some great new people, chatted and laughed with old acquaintances, and had some thought provoking conversations, and really good food.
The most touching thing of the evening was on the way out. John Heath, another partner in The Brenner Group, was by the exit, giving away a copy of Core Memory "A Visual Survey of Vintage Computers" with page after page of photographs by Mark Richards and accompanying text by John Alderman. Another commemoration of 20 great years in the valley and of The Brenner Group. Congratulations to all.
On a side note, I did have a longer than expected drive home, as I was stopped by the tunnel construction on Devil's Slide. These two shots from my cell phone show the traffic and warning sign ahead and yes that is the ocean beyond the cleft in the mountain, and one of the reasons I live on the coast is the view to my right of the twilight sky over the Pacific.


Guy Kawasaki's advice is that a position at a VC is to be taken at the end of one's career, not the beginning. This is somewhat reminiscent of thoughts and discussions that I had in my early days in the rocket factory [my second career]. My advice at the time for those pursuing a career in engineering was that one's first position should be as a quality assurance test technician, so they could learn the consequences of poor design; then move into increasingly more responsible engineering design positions, and [if they hadn't moved into project, program or line management] go back to QA, where they could truly apply their experience to improve the product.
Perhaps the same could apply to any career path. For VCs: intern with a VC firm, then get "in the trenches experience" in engineering, sales, entrepreneurial ventures, large and small public companies, taking and making investments, success and failure, and then go for the full-tilt boogie, fly in private jets/expense the greens fee VC position.
And yes, I took the VCAT. I think I need to get Walt Mossberg's number to score higher. ![]()
Today at the ANZA Technology Network conference, I attended the Funding your Business in the US Forum. This year ANZA video taped all of the sessions. Viki Forrest, the CEO of ANZA introduced the moderator, Kevin Matsushita, Vice President Emerging Technology Practice, Silicon Valley Bank, and panelists:
Here are some of the things I took away from this session.
Many of these points I've heard many times over the years. One thing I would like to add is that as a founder of a company, one should always be reevaluating their position in the company and should ALWAYS hire a person to do a job better than they could do it themselves. That always applies, whether it is choosing partners as co-founders, hiring to fill out the management team, building out the full team AND MOST ESPECIALLY when looking at your successor for the many roles you'll fill throughout the life of your baby, er, company. You may start out as Chairman, CEO, President, lead technologist, lead sales, and chief cook and bottle washer. You may change roles as the company grows. You must always be aware that your role(s) at one stage of your company's life may be better served by someone else at later stages. The other part of this is that you must be able AND WILLING to delegate both work AND RESPONSIBILITIES. The two must be commensurate.
As an entrepreneur, you should also be looking for complimentary talents and personalities to your own and your initial team. This is as true for the investors you may get as it is for your operational team. And always have fun.
Clarise and I attended the PMI [of which we're members] San Francisco Bay Area April supper meeting last night. The topic, "The Natural Evolution of a PMO", is of interest to us because we've been unable to determine if something really new is happening here. The answer is NO. As we suspected, PMO is hype to get companies to establish standard project management methodologies, such as our own 6D™ methodology, complete with procedures and templates. One evidence that this is so, is that there isn't agreement on whether the "P" in PMO is "project" or "program".
As so often happens, the most interesting talk of the evening was that at the supper table with our colleagues. One topic of conversation was on the wiki(Theory of Constraints) and wiki(Critical Chain) Project Management. Managing a project is about managing resources, and Critical Chain Management addresses managing conflicting demands on resources. As Pat, at our table, pointed out, one doesn't necessarily have the data necessary to actually use the Critical Chain model. I liken it to Chaos theory in mathematics; great for understanding what occurred or is occurring, but it isn't so good as a predictive model. So if one can't adequately plan [model] a project using Critical Chain, does it have any value? Perhaps... Create a knowledge base of all projects in the portfolio, and use Critical Chain to understand what happened in the projects and why projects succeed or fail in your corporate environment.
Here's a google search that provides some nice results for Critical Chain in Project Management.