Rands on the Status Report

Status: Interviewed Bob for the engineering positioning.
Context: Continued to interview candidates because our front-end engineering team is currently 1/3rd the size of our platform team which means we can’t put a well-designed face on most of the functionality we’re building.

Rands lays into the status report and advocates instead for a context report — offer status and an explanation of why the status is important. In an age of distributed task tracking tools (Jira? Basecamp?) a manager should be able to get a basic list of completed tasks without too much difficulty, but the why is just as inscrutable.



I’m a senior product manager for OpenTable’s consumer products. I focus on major features, including our loyalty program, diner profiles, social integrations, and new business exploration.