Andrew Luxem

The 3Ps Framework: Turn weekly activity into progress, plans, and problems

A weekly update lists meetings, tickets, and drafts but leaves the reader unable to tell what changed, what happens next, or what needs help. This brief shows the mechanism, failure check, and adoption test.

Andrew Luxem
Andrew Luxem
CRM, Lifecycle & AI Strategy

2 min read
The argument
A weekly update lists meetings, tickets, and drafts but leaves the reader unable to tell what changed, what happens next, or what needs help.
The skill should turn weekly activity into progress, plans, and problems.
Run four weekly cycles. Count how many Plans move to Progress and how many Problems close by their due dates.

A weekly update lists meetings, tickets, and drafts but leaves the reader unable to tell what changed, what happens next, or what needs help.

The useful response is not more ceremony. It is a mechanism that can turn weekly activity into progress, plans, and problems.

What the skill produces

The The 3Ps Framework skill turns supplied context into one short update with measurable progress, dated plans, and blockers with owners and asks. It should expose missing evidence instead of inventing it. The free skill packages this mechanism for explicit use. It does not fetch remote instructions, and the practitioner remains responsible for the facts and final decision.

Run the mechanism

  1. Compare completed work with the prior plan.
  2. Write the next commitments with owners and dates.
  3. Name each blocker, its owner, and the specific help required.

The owner should review the output against the original evidence before it is used. Any unresolved assumption stays labeled, with an owner and date when it affects the decision.

Failure check

The headings do not create discipline when Progress contains activity, Plans omit dates, or Problems hide the ask.

Adoption test

Run four weekly cycles. Count how many Plans move to Progress and how many Problems close by their due dates.

Keep the skill only if it improves the artifact or decision against that baseline. Revise the playbook when the same failure survives more than one review cycle.

Infographic

ACTIVITY IS NOT AN UPDATE infographic
Andrew Luxem
20 years building CRM and lifecycle programs at Amazon, Ancestry, and Stanley Black & Decker.