Product and project planning has its own figurative vocabulary: pipelines, north stars, runways, freezes, and creep.
These idioms appear in roadmap discussions, OKR meetings, sprint reviews, and investor updates.
Understanding them helps you participate confidently in strategic conversations.
Intermediate5 exercises
Question 1 of 5
A product manager writes in the team wiki: "The dark mode feature is in the pipeline — we'll schedule it for Q3." What does in the pipeline mean in this context?
In the pipeline originally refers to oil flowing through a pipe — it's on its way but hasn't arrived yet. In product and tech, it means: "planned, acknowledged, and under some level of development, but not yet shipped." It's used to manage expectations without making a firm commitment. Related expressions: "on the roadmap" (planned for a future release), "on the backlog" (logged but not yet prioritized), "in progress" (actively being worked on right now). Career tip: if you're asked about a feature in a user interview, "it's in the pipeline" buys time without over-promising.
During a sprint review, the engineering lead says: "We've been dealing with scope creep — three new requirements were added mid-sprint, and now we can't deliver the original stories." What is scope creep?
Scope creep is the uncontrolled or gradual growth of a project's scope — new features, requirements, or deliverables that are added without adjusting the timeline, budget, or resources. It's one of the top reasons projects are delayed. "Creep" suggests slow, almost invisible movement — it sneaks in through small agreeable changes that accumulate into a major problem. Agile methodology addresses this with a defined sprint scope that shouldn't change once the sprint starts. How to counter it: "That's out of scope for this sprint — let's add it to the backlog." Or: "That's a scope change — it will require adjusting the timeline."
The VP of Product writes in the company OKR document: "Our north star metric this quarter is weekly active users — every feature decision should serve that goal." What is a north star metric?
North star metric borrows from navigation: the North Star (Polaris) is always in the same direction, guiding ships across the ocean. In product strategy, the north star metric is the one number that best represents the product's core value — and if it grows, the business is healthy. Popularized by companies like Facebook (daily active users), Airbnb (nights booked), and Spotify (time listened). The metaphor implies: all decisions should point toward this goal, just as a ship's course points to the north star. Watch out: optimizing for the wrong metric can grow a number while hurting the product (e.g., maximizing sessions by making the product confusing).
A startup founder says to investors: "We have 18 months of runway at our current burn rate — enough time to reach profitability." What does runway mean here?
Runway comes from aviation: it's the length of runway an aircraft needs to take off. If it's too short, the plane doesn't make it. In business and startups, runway = how long you can keep operating before you run out of money. Calculated as: current cash / monthly burn rate. "We have 18 months of runway" means the company can survive 18 months without new revenue or investment. It's a critical startup health metric. Related: "burn rate" (monthly spend), "bridge financing" (short-term funding to extend runway), "ramen profitable" (making just enough to keep the lights on). Developers may hear this term during all-hands meetings or when discussing the business impact of features.
The engineering director announces: "We're entering feature freeze on Friday — no new features after that, only bug fixes and stabilization before the release." What is a feature freeze?
Feature freeze is a controlled cutoff point in the release process: after this date, no new functionality can be added to the release. The goal is to give QA and the release team a stable, known set of changes to test and deploy. "Freeze" is an apt metaphor — the feature set is locked in place, like water frozen into ice. Common in large software projects, game development, and enterprise releases. After feature freeze, the team focuses on: regression testing, performance optimization, critical bug fixes, documentation updates. Breaking a feature freeze is a serious decision requiring management sign-off. Also called "code freeze" when it extends to all changes.