Remove Engineering Remove Systems Review Remove Technical Review
article thumbnail

Ask Teresa: Does the Engineer in the Product Trio Need to be the Tech Lead?

Product Talk

Without input from a product manager, a designer, and an engineer, it’s difficult for us to account for the cross-functional perspectives we need to build successful products. However, most companies tend to have more engineers than product managers or designers. Which engineers should participate in trios?

article thumbnail

523: #1 change to make OKRs work for you – with Ben Lamorte

Product Innovation Educators

Understanding OKRs: From Intel to Modern Product Teams The evolution of Objectives and Key Results (OKRs) began at Intel during the 1970s and 1980s, where Andy Grove transformed the traditional Management by Objectives (MBO) system into something more dynamic and outcome-focused.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Understanding Product Management

The Product Guy

Relative to other standard roles defined in an organization such as Ops, Marketing, Tech etc., Often, this is due to resource constraints rather than a lack of understanding of a PM role. This includes Tech estimates (at least T-shirt sizing) and resources identified for the projects. Hard Skills Required for the Role.

article thumbnail

Technical Review: A Trusted Look Under the Hood

TechEmpower - Product Management

Most innovators don’t have a technical background, so it’s hard to evaluate the truth of the situation. And unless they have a tech background, they can’t look under the hood themselves. The answer is to engage a trusted outside source for a Technical Review – a deep-dive assessment that provides a C-suite perspective.

article thumbnail

Strategy Blocks: An operator’s guide to product strategy

Lenny Rachitsky

Step 1: Preparation (3-5 weeks) The preparation step is a foundational effort where a lot of the groundwork and due diligence is done to inform the strategy selection process. These illustrative concepts are not intended to be “shovel-ready” for engineering to build on. This could include the founders, CEO, etc.

Strategy 116
article thumbnail

Core responsibility: How we scaled our core technologies team

Intercom, Inc.

It’s a familiar problem for all companies that scale fast – how do you keep your core technologies manageable for the increasing number of teams that depend on them? This surfaced as an increasingly large percentage of our product teams’ time being spent on operations or deep diving into understanding our small set of core technologies.

article thumbnail

Words matter: Removing exclusionary terminology from our codebase

Intercom, Inc.

And while seeing this work come to fruition, Sam, a Product Engineer at Intercom, was inspired to find more ways to get involved. As she tells it, “When I was fresh out of college, I was working at my first job in the tech industry. Think about the impact that racism has already had in tech. Know the scope of the issue.