AI product launch coverage typically focuses on what a new release includes. What's comparatively rare is coverage of what was promised at an earlier announcement and then quietly dropped, delayed indefinitely, or scaled back by the time the product actually shipped-even though this pattern is common enough, and informative enough about a company's execution and honesty, to deserve more attention than it usually gets.
Why dropped features are hard to track
There's no standard mechanism for tracking a company's promised roadmap against what actually ships, which means catching a quietly dropped feature requires an outlet to have covered the original announcement closely enough to notice its absence later, and to be willing to revisit older coverage rather than treating each launch as a fresh, standalone story disconnected from previous promises.
Why this pattern matters
A company's track record of shipping what it announces, on roughly the timeline it announces, is a genuinely useful signal for evaluating how much weight to give its next announcement. A pattern of ambitious announcements followed by quietly scaled-back or delayed delivery is informative in a way that a single launch story, evaluated in isolation, can't capture.
What more accountable product coverage looks like
Useful product coverage would maintain some memory across a company's announcement history, explicitly noting when a shipped product falls short of an earlier promise, rather than covering the shipped version as though the earlier, more ambitious announcement never happened. This is more work than covering each launch fresh, but it's what actually holds companies accountable to their own stated roadmaps.
Our approach
Where we've covered an earlier, more ambitious announcement from a company, we try to note explicitly when a subsequent launch falls short of what was originally promised, because that gap is often more informative for readers evaluating the company's credibility than the launch itself.