What do we struggle with most of the time?

Eating the elephant. In product development, even more so.

We look at an entire product, end-to-end, and get overwhelmed by its complexity, size, and time duration.

Time to look at some old wisdom.

“Nothing is particularly hard if you divide it into small jobs.” – Henry Ford

You have a choice to break work down into smaller jobs or tasks. As well, as to estimate the relative size of the work being done.

P.S. What are some of the work estimation and breakdown techniques you use?

I’m not a software developer.

Alternatively, I’m a technology geek and nerd. You don’t need to write code to be in the technology field.

The snippet below is from my transcript. It proves that there is a place for folks in technology who do not code.

Successful software product development teams have diverse members. They cover a range of disciplines beyond the building process.

Are your dev teams diverse?

Equally important, do your dev teams have people from non-traditional backgrounds?

To effectively solve complex and wicked problems, we need people from many backgrounds to join the product development space.

P.S. Do you think software developers should work in other professional fields to build empathy for the people they create products for?

The picture below shows the first product I built as part of a team.

Pretty impressive, even more so seeing all the pieces come together over two years.

It takes 10s of 1,000s of hours to design and build a nuclear submarine. As well, 1000s of people in the process.

The WYOMING was delivered to the U.S. Navy ahead of schedule.

Having high performing teams involved in the process cannot be underestimated.

Cultural excellence influenced its delivery as well.

Consider those points as you start the week.

P.S. Would you share your best product development experience?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26