It’s Monday morning. You open a blank document to write your weekly update. You list the tickets your team closed, the meetings you had, the metric that wiggled up two percent. You hit send. It’s an accurate account of the past seven days. It's also completely useless.
Most product reports are history books. They are passive archives of what has already happened. They fulfill an obligation but inspire no action. Stakeholders skim them, file them away, and nothing changes. This is because a history book requires nothing from the reader.
Stop writing history books. Start writing contracts.
A contract is an active document. It’s an agreement about the future based on the reality of the present. It creates clarity, establishes accountability, and forces a conversation. When you treat your weekly report as a contract, it stops being a chore and starts being one of your most powerful tools for alignment.
A contract has three parts.
1. Honoring Past Commitments
This is your accountability section. It replaces the bland "What we did" list. Start by restating exactly what you promised to do last week. Then, state the outcome.
- Don't say: "We launched the new checkout button."
- Do say: "Last week, we committed to launching the new checkout button to 10% of users to test its impact on conversion. We launched on Wednesday. So far, the conversion rate for the test group is 1.2% lower than control."
You are publicly grading your own homework. It builds trust, even when you fail. It shows you are paying attention and holding yourself to a standard.
2. Stating Present Reality
This is the context. The "whereas" clause of the contract. Based on the outcome of your last commitment, what is true now? This is where your data and qualitative insights live, but they aren't just a disconnected list of facts. They are the direct justification for what comes next.
- Don't say: "Conversion is down. We also got some user feedback."
- Do say: "That 1.2% conversion dip is a bigger drop than we modeled. Looking at session recordings, users are hovering over the button but not clicking, and feedback tickets mention confusion about the 'apply coupon' step. Our hypothesis is that the new design is less clear than the old one."
This section connects the past to the future. It’s the narrative bridge that explains why you are proposing the next set of terms.
3. Proposing New Commitments
This is the most important section. This is the "therefore" clause. Based on the reality you just described, what are you committing to this week? Be specific. Be falsifiable. This isn't a vague wish list; it's a set of deliverables.
- Don't say: "Next week, we'll work on improving the checkout flow."
- Do say: "Therefore, this week we commit to two things: 1) Ship a UX copy change to the button by Tuesday to clarify the coupon step. 2) Build a dashboard to monitor conversion for this cohort in real-time. We will defer the planned work on user profiles to address this revenue risk."
This is an offer. It invites your stakeholders to engage. A sales leader can read this and say, "Good, I was worried about that dip." Your engineering manager can see the clear, limited scope. Your GM can read it and trust you're focused on the right problem. Or, they can disagree. They might say, "No, the user profile work is more important, we can live with the dip." That's a productive disagreement. That is alignment.
Your report is no longer a passive update to be archived. It is a proposal to be accepted, debated, and acted upon. It forces you to think critically about your priorities and makes it easy for others to understand your logic. Stop documenting the past. Start defining the future.