Objective

What this project set out to do

[OBJECTIVE — one or two sentences, no more. State the goal in plain language, not deliverables. Resist adding context here; that belongs in Challenges.]

Challenges

What made this hard

[FRAMING — two or three sentences of context. If the challenges are not genuinely distinct, delete the tile row below and keep this section text-only.]

Approach

How the work was structured

[APPROACH — describe the shape of the engagement: phases, who was involved, what decisions each phase fed. Keep the detail of individual methods for the Methodology section.]

Methodology

Methods, and why each one

[METHODOLOGY — lead with the reasoning: what question each method was chosen to answer, sample sizes, and any limitations you would name in a viva. Only keep the tile row below if the methods are genuinely distinct; otherwise delete it and let this paragraph carry the section.]

Solutions & Findings

What we found, and what we built from it

[FRAMING — one short paragraph. Let the tiles below carry the detail; this paragraph only needs to set up how to read them.]

Recommendations

What was recommended, and what shipped

[RECOMMENDATIONS — be specific about what you proposed, what was implemented, and what was not. Naming what did not ship, and why, reads as more credible than a list of wins. Delete the before/after row below if you have no comparable visuals.]

Impact

What changed as a result

[~25%]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

Outcomes

Where it landed

[OUTCOMES — a short summary of the end state. Where Impact is numbers, this is the narrative: what exists now that did not before, who owns it, and what happened after handover.]

Reflections

What I would do differently

[REFLECTIONS — first person, and specific. Name the decision you are least sure about and what you would test instead. This section is more convincing when it is not flattering.]

Learnings

What transfers to the next project

[LEARNINGS — what you would carry into unrelated work. Keep these portable; a learning that only applies to this client is really an outcome.]

  • [LEARNING 01 — stated so it would still make sense to a stranger.]

  • [LEARNING 02 — stated so it would still make sense to a stranger.]

  • [LEARNING 03 — stated so it would still make sense to a stranger.]

© 2026 by Joel Mathew. All Rights Reserved.

Objective

What this project set out to do

[OBJECTIVE — one or two sentences, no more. State the goal in plain language, not deliverables. Resist adding context here; that belongs in Challenges.]

Challenges

What made this hard

[FRAMING — two or three sentences of context. If the challenges are not genuinely distinct, delete the tile row below and keep this section text-only.]

Approach

How the work was structured

[APPROACH — describe the shape of the engagement: phases, who was involved, what decisions each phase fed. Keep the detail of individual methods for the Methodology section.]

Methodology

Methods, and why each one

[METHODOLOGY — lead with the reasoning: what question each method was chosen to answer, sample sizes, and any limitations you would name in a viva. Only keep the tile row below if the methods are genuinely distinct; otherwise delete it and let this paragraph carry the section.]

Solutions & Findings

What we found, and what we built from it

[FRAMING — one short paragraph. Let the tiles below carry the detail; this paragraph only needs to set up how to read them.]

Recommendations

What was recommended, and what shipped

[RECOMMENDATIONS — be specific about what you proposed, what was implemented, and what was not. Naming what did not ship, and why, reads as more credible than a list of wins. Delete the before/after row below if you have no comparable visuals.]

Impact

What changed as a result

[~25%]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

Outcomes

Where it landed

[OUTCOMES — a short summary of the end state. Where Impact is numbers, this is the narrative: what exists now that did not before, who owns it, and what happened after handover.]

Reflections

What I would do differently

[REFLECTIONS — first person, and specific. Name the decision you are least sure about and what you would test instead. This section is more convincing when it is not flattering.]

Learnings

What transfers to the next project

[LEARNINGS — what you would carry into unrelated work. Keep these portable; a learning that only applies to this client is really an outcome.]

  • [LEARNING 01 — stated so it would still make sense to a stranger.]

  • [LEARNING 02 — stated so it would still make sense to a stranger.]

  • [LEARNING 03 — stated so it would still make sense to a stranger.]

© 2026 by Joel Mathew. All Rights Reserved.

Objective

What this project set out to do

[OBJECTIVE — one or two sentences, no more. State the goal in plain language, not deliverables. Resist adding context here; that belongs in Challenges.]

Challenges

What made this hard

[FRAMING — two or three sentences of context. If the challenges are not genuinely distinct, delete the tile row below and keep this section text-only.]

Approach

How the work was structured

[APPROACH — describe the shape of the engagement: phases, who was involved, what decisions each phase fed. Keep the detail of individual methods for the Methodology section.]

Methodology

Methods, and why each one

[METHODOLOGY — lead with the reasoning: what question each method was chosen to answer, sample sizes, and any limitations you would name in a viva. Only keep the tile row below if the methods are genuinely distinct; otherwise delete it and let this paragraph carry the section.]

Solutions & Findings

What we found, and what we built from it

[FRAMING — one short paragraph. Let the tiles below carry the detail; this paragraph only needs to set up how to read them.]

Recommendations

What was recommended, and what shipped

[RECOMMENDATIONS — be specific about what you proposed, what was implemented, and what was not. Naming what did not ship, and why, reads as more credible than a list of wins. Delete the before/after row below if you have no comparable visuals.]

Impact

What changed as a result

[~25%]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

[00]

[WHAT IT MEASURES]

[Source and period.]

Outcomes

Where it landed

[OUTCOMES — a short summary of the end state. Where Impact is numbers, this is the narrative: what exists now that did not before, who owns it, and what happened after handover.]

Reflections

What I would do differently

[REFLECTIONS — first person, and specific. Name the decision you are least sure about and what you would test instead. This section is more convincing when it is not flattering.]

Learnings

What transfers to the next project

[LEARNINGS — what you would carry into unrelated work. Keep these portable; a learning that only applies to this client is really an outcome.]

  • [LEARNING 01 — stated so it would still make sense to a stranger.]

  • [LEARNING 02 — stated so it would still make sense to a stranger.]

  • [LEARNING 03 — stated so it would still make sense to a stranger.]

© 2026 by Joel Mathew.

All Rights Reserved.