Messaging the direction

Read this great post on AVC today ::

It reminds me of some thoughts on product management – then I realized how I had written up this multi-parter but never got past part 1. oops.

Let me add my point – which is based on this comment from Fred:

The number one cause of employee unhappiness and unwanted departures is “I don’t understand where we are going.” That is a failure of leadership on the CEO’s part. I agree with John, keep it simple and repeat often and don’t mix up your messages. It is critical, particularly as the organization grows in size.

One of the hardest problems I faced with teams small or large was keeping everyone on the same page and making sure the product management process aligned with the business process. It would be easy to find work to do or to evolve a product or a feature or just let a dev work on something “cool”. Problem is though that all those things may not help solve a business goal. 

The issue is you need to convey to the product team where the company is going and how the product cadences will help the company meet the business goals. There is no perfect way to manage all of this but what started to work for me was having 6 month big picture meetings where business goals where stated and the product roadmap would be discussed as a group but with the clear idea that the product needed to support the business needs. Then we would try to break things down by quarter and by month. At a product level we might even get down to 2 week sprints. 

At the beginning of the 6 months, post the big pow wow meeting, everyone knew where we were going and everyone knew their role in the outcome. This helped with dealing with wayward devs or product creep but this also helped deal with the other side of the coin which is when the biz folks would change their mind midstream. I think it is important to hold both sides accountable – if you stick to the plan then normal schedules are okay but if the biz people want to alter the course, which is perfectly okay, then the biz people must accept that the product schedule will get pushed back. 

This way everyone knows the plan, everyone knows how to make it work and everyone is accountable for time changes if there are scope changes. It is not easy. No amount of tools make it easier but making sure everyone knows where the biz is going and how is an important step in how product management works.

Great post by Om on Empathy

I am digging seeing Om in long form in the New Yorker ::

He makes some solid points but I don’t see the valley changing much given it’s such a bubble. Both the wealth and the protection from the real world but I do wonder how the Trump era is going to attack it and how the valley will rise to the challenge.

Empathy would be a great place to start.

I have talked about this some before ::

Thoughts on schooling 

This is pretty interesting ::

Obviously a work in progress but it feels like the right way to try and tackle a new period of education.

I don’t know what the right answer is to how best to educate kids. Even with my own kids I struggle a bit since I would choose options other than Singapore public schools but the options are not much better and vastly more expensive.

I have done some private school, some home school, some public school but very little university – my views are all over the place but my most enjoyable school experience was 4-8th grade. One room classes with one teacher and an assistant who took us through all of our courses, read books to us and introduced me to computers. Small classes with teachers who cared and who had also had other careers in their past – they were not teachers from day one. 

This actually may have been the difference – since they brought in their previous experiences and shared bits about real life and career theories.

Looking back I am pretty sure those 4 years of school were my most formative. I one day aspire to teach some after I retire.