Frameworks for growing your product, career, and impact with Bangaly Kaba

Executive overview

Most product and career problems trace back to a mismatch between environment, skills, and where you focus your energy. Bangaly Kaba's career framework makes that mismatch visible and scoreable, so you can act on it rather than just feel it.

The same clarity discipline applies to product growth: teams that build without first understanding the problem ship things that don't move metrics. His antidote — understand work — is a deliberate, time-boxed allocation of team bandwidth to de-risk execution before it starts.

Slowing down to understand is the fastest path to compounding growth.

The career impact equation: environment × skills

• Impact is the core output to optimise — compensation and levelling follow from it, not the other way around.
• Environment has six scored variables: manager, resources, scope, team, compensation, company culture.
• Manager is the most important variable — a great manager can fix most of the others; a bad one can break them all.
• Score each variable quarterly (0–2 scale); be honest about what's limiting impact and whether it can change.
• When the score reveals a structural mismatch, consider changing the variable before changing the job.
• Skills to build: communication (highest leverage), influence and leadership, strategic thinking, execution.
• A stable of three to four mentors — one per Friday — beats a single mentor; continuity is the point.
• Build skills by watching others practise, not just reading theory: sit in team meetings, steal what works.

Understand, identify, execute — not the other way round

• The anti-pattern: identify a good idea → justify it with data → execute → metrics are flat.
• Understand work is an explicit, planned affordance on the roadmap — it doesn't happen automatically.
• Every function contributes: engineering instruments logging; data science builds proxy metrics; PM maps the funnel; go-to-market surfaces blockers early.
• Run execution and understand work in parallel every sprint; use both outputs to plan the next one.
• The ratio shifts over time: new teams may start at 60% execution / 40% understand; mature teams reach 85% / 15%.
• Result: higher win rate per experiment, higher velocity — Instagram teams were shipping 12–20 experiments per quarter per team with a 60–70% positive rate.

Managing complex change in teams

• Framework: Vision + Skills + Incentives + Resources + Action Plan — remove any one and you get a predictable failure mode.
• Missing vision → confusion. Missing incentives → resistance. Missing action plan → false starts.
• Action plans are the easiest to fix; vision and skills take longer.
• Build a portable deck of frameworks and mental models to give new teams a shared language fast.
• Bloom's Taxonomy maps where a PM is stuck: knowledge → comprehension → application → analysis → synthesis → evaluation; diagnose before prescribing.
• Managers need to live at the top of the pyramid across all their teams — synthesising, not just executing.

Adjacent user theory and growth flywheels

• Adjacent user: the person just outside your current user base who could use the product but doesn't — yet.
• In hypergrowth, your users six months from now are fundamentally different from your users today; cohort curves declining is the signal.
• Mandatory for hypergrowth companies; highly useful for any product that has hit a growth ceiling.
• Dog-food the product as an adjacent user, not as a power user — they experience a categorically different product.
• At Instagram: women in their 30s in early 2016 said "I have Facebook, why would I use Instagram?" — a year later it was their primary platform.
• Growth flywheels stack: Instagram combined invitations + celebrity partnerships + SEO + embeds + paid media; each engine magnified the others.
• Web launch alone drove a 10% immediate growth lift by creating canonical SEO pages, which amplified celebrity partnership coverage in news media.
• At Instacart: 90% of a cart after five orders was the same items, but reordering required seven to eight clicks — fixing that was a direct retention lever.

The connections pivot and activation at Instagram

• Early Instagram treated all follows equally — celebrities surfaced first, crowding out friend connections for new users.
• New users built a celebrity-heavy graph, posted for the first time months later, got no likes or comments, and quietly stopped using the product.
• The connections pivot (2016–17): prioritise human-to-human connections during onboarding; celebrities come after the graph is established.
• Retention roughly doubled over 18 months as a result.
• Account access churn was losing 10–12 million users per year: people couldn't remember which email or handle they used.
• Fix: Omnibox login (email, phone, handle in one field) + trusted-device SMS prompt + save-credentials prompt on logout.
• Side effect: recovering account access surfaced heavy second- and third-account usage, which spawned the multiple accounts team.

Lessons from Facebook's people graph in India

• People recommendations in India were breaking: far fewer mutual friends than in the US, high friend-and-unfriend rates.
• On-the-ground research revealed Western profile fields (school, job title) were irrelevant; 250,000 people per month were named Amit Kumar.
• Users navigated identity through photos — car, animal, visual context — not profile metadata.
• Understand work in-market produced insights no amount of A/B testing from Menlo Park would have surfaced.

Coaching product teams

• PM is a team sport; the role is coach, not CEO.
• Not every PM needs to be a star player — strong role players in the right seats compound team output.
• Think in terms of a coaching tree: who are you developing to become leaders elsewhere? Their success is your legacy.
• New leader first 90 days: sit in team meetings and listen; learn everyone by name and story before sharing your views.
• People who've left a company give you the raw, unvarnished version — talk to them before joining.

Career fail corner: Instacart

• Went in with a vision for where the product could go; underestimated that the company needed tactical, hands-in-the-funnel execution at that stage.
• Misread the DNA: Instacart was an operations company building up its product muscle, not ready for the systems-and-process layer he was building.
• Lesson: talk to people who've left the company, not just those who are there — insiders sell the best version; alumni triangulate it.