LINKEDIN PROCESS EXPLANATION POST TEMPLATE
Bravabase — free writing template
Source: https://bravabase.ai/templates/linkedin-process-explanation-post/
Updated: 2026-10-18

WHEN TO USE IT
Use this when a prospective client cannot see what happens between a brief and a deliverable. Choose one stage you can explain accurately. A process post demonstrates a method; a case study reports an actual project and its outcome. If you have not yet used the method, present it as a proposed approach rather than your established practice.

GATHER YOUR NOTES
- The specific task or stage you are explaining.
- The material you need at the start.
- Two or three checks you actually make, including one decision that changes the path.
- A small invented example or an approved, anonymized example.
- The output and the work that still remains afterward.

YOUR DRAFT
What happens when [task reaches you]?

I start with [input], rather than [premature action].

Here is the sequence:
1. [Check] — so we can decide [decision].
2. [Check] — if [condition], we [branch].
3. [Action] — producing [output].

A small example: [label the example and show the input].
That leads to [specific output or next decision], because [reason].

At this point we have [what is ready]. We still need [what is not finished].

[Question about the step readers want explained.]

FICTIONAL WORKED EXAMPLE — NOT YOUR PERSONAL HISTORY
Fictional example: a messaging consultant demonstrates how they turn a vague homepage brief into a page outline. The notes and draft below are invented to illustrate the explanation; no client outcome or conversion improvement is claimed.

NOTES BEHIND THE DRAFT
Input: An invented brief says: “Show all our capabilities and get more enquiries.” The service is a handoff review for small agencies.
First decision: Which visitor situation should the page address? Choose a project with unclear ownership between teams.
Evidence check: The brief has a clear deliverable but no approved customer results. Explain the work without adding performance claims.
Output: An outline covering the situation, review steps, deliverable and scope boundary. Copy, design and testing are still to come.

POST EXAMPLE
What happens before I write a service homepage?

I start with the decision the page needs to help a visitor make. “Show all our capabilities” does not tell me that yet.

Here is the sequence:
1. Name the visitor situation. What is happening when this service becomes relevant?
2. Check the evidence. What can we explain or show, and which claims are still unsupported?
3. Outline the page around that decision before writing finished copy.

Take this invented brief: an agency adviser offers a handoff review, but the homepage currently lists every service they could provide.

I would start the outline with the moment work moves between teams and ownership becomes unclear. Then I would explain the review, the checklist it produces and what is outside its scope.

If there are no approved customer results, I would describe the deliverable. I would not add a claim that it reduces delays by a particular amount.

Now we have a page outline to discuss. We do not yet have finished copy, a design or evidence of how visitors will respond.

Which part of your service needs a clearer explanation before someone can decide whether it fits?

REVIEW BEFORE PUBLISHING
- Is the method something you use, or clearly labeled as an approach you propose to test?
- Can the reader identify the input, a meaningful decision and the output?
- Does the example show the process without exposing private client material?
- Have you distinguished the deliverable from an unmeasured business result?
- Would a reader understand what still needs to happen after this stage?

NEXT STEP
Format your reviewed draft: https://bravabase.ai/tools/linkedin-text-formatter/
Try Bravabase: https://app.bravabase.ai/signup
7 days free. No card required. You approve every message and post before it goes out.