Read - Write - Experiment - Unlearn - Relearn

Over a point in time, once we collect/analyze trends/patterns we will have our perceptions of how things are shaping up

• Customer data patterns
• Product adoption vs predictions
• Gartner hype vs Reality

Bring it down to 300 feet when solving day to day vision, forecasting, recommendations, and data problems

• Alternatives
• Algos / Data challenges
• Vision options models / custom training / alternative approaches

The mind always keeps things looking out 

• Running thoughts of options / references / ideas
• Experimenting with codes and evaluating pros/cons
• Planning for next steps / next aspects of product building
• Agile / Calculated risks / /Proactive to spot failures
• Plan for the team, Don't miss anything to waste team efforts
• Learn and upskill self, to guide / proactively spot red flags
• Use experience to apply and identify risks
• Being productive not just busy needs a running set of ideas/thoughts
• Reduce the gaps between Great planning vs Poor Execution

The mind always keeps on what next to anticipate, and prepare for .....

Keep Going!!!

Good Idea - needgap.com - Product Ideas Discussion

Something similar to hackernews but more of product ideas validation needgap. Good place to validate ideas.

Keep Exploring!!!

How quick to learn ?

• Know your end goal, What you want to accomplish
• Know where to lookup for good short lessons (Github / Blogs / Books / Youtube video)
• Follow the path few sources
• If all steps fail, take a break and come back again. Sometimes we need a break to get a new perspective
• Save your steps - Navigation links / Commands
• Reach out to StackOverflow / friends who are experts in that area
• Document your working Steps
• Share it to your wider audience in your books/blogs
• Everyone has a way of doing things / When you learn from some source you also need to be a learning source to someone else

A solution can be built in multiple ways, You must have a working skeleton of your thoughts before you look to optimize it.

Keep Learning!!!

Products are built to fail.

In many ways underestimate the impact of domain knowledge. Can we have one forecasting algorithm for

• Retail Product Sales
• Oil Sales
• Stocks Predictions
• Car Sales 

If everything can be built just by one algorithm we would need to close all ML shops in a month. We underestimate domain knowledge and believe fancy tech and tools will have the ability to read and give all the fine-tuning. 

Keep Going, Sometimes tech does not understand business, and products are built to fail.

Knowledge is 

• Mapping business to tech to support futuristics ways of new business changes
• Making it flexible to scale, port, migrate
• Think Business first, Scale next, Tech at last

What is the new learning format

• Domain understanding - Technology evolves faster than we think. New forms of business evolve
• Data understanding - Know the type of data - speed / slow data
• Research paper - Insights / Blogs - Look for Leaders in the space and their tech stack, Look for research papers and insights
• Model development / Model implementation

Keep Thinking!!!

Metrics of product building

However, we have sprints/process/domain expertise. 

• What is the measure of how much we know the product perspective, vision vs implementation
• After few sprints how do product and business feel about the outcome, Are they in line with what is developed vs envisioned
• Everyone has a way of conveying/thinking their perspective, How do we call out / communicate all the business flows and ensure we keep everyone on the same page
• How much of the team believes / inline with the storyline and implementation
• Tech stack never ends, business domain learning, new trends keep popping up. 

I have less time left, Its better to fight selective battles, I recognize my time is less when I near 40s

Keep Thinking!!!