The BER Reflection

September has arrived.

With it come the final four months of the year: September, October, November and December — the BER months.

We often experience them as a countdown. Time to finish the targets, rescue unfinished plans, prepare for Christmas, close the year and start thinking about the next one.

But perhaps these four months can serve another purpose.

Not simply four months to finish the year, but four months to learn from it.

I call this The BER Reflection: a simple four-stage practice for moving deliberately from experience to understanding, from understanding to development, and from development to intentional commitment.

It is also one practical expression of a wider idea I describe as Reflective Intelligence: strengthening the human space between what we experience or receive and what we decide to do next.

The distinctions between the four stages matter.

September — Discover

What actually happened?

Before deciding whether the year has gone well or badly, first establish what happened.

Memory is selective. Disappointment can make us overlook progress, while success can hide difficulties that still deserve attention. Discovery therefore begins with evidence rather than judgement.

Ask three questions:

What happened that mattered? What changed? What evidence do I have?

Your evidence does not have to be dramatic.

A September inventory might contain entries as ordinary as:

• A project planned for June moved to September after two new priorities were added.
• Feedback on my client work remained positive, but I repeatedly struggled to protect time for longer-term development.
• I stopped doing my weekly review in May, and my workload became increasingly reactive afterwards.

Notice what these statements do not contain.

They do not yet say why any of those things happened or who was responsible. They simply make the experience visible.

Achievements, disappointments, decisions, conversations, feedback, changed circumstances, abandoned plans and unexpected opportunities can all belong in the inventory.

September is not the month to explain everything.

It is the month to produce an honest evidence inventory.

See clearly before interpreting quickly.

October — Discern

What does it mean?

Facts and interpretations are not the same thing.

Looking at the September inventory above, someone might conclude:

That may be true.

But it is not the only interpretation supported by the evidence.

Two new priorities were added. Longer-term work repeatedly lost protected time. A useful review practice disappeared as the workload became more reactive.

Perhaps greater discipline is required. But the evidence may point instead — or additionally — towards weak prioritisation, insufficient boundaries, an overloaded system or the absence of a reliable review rhythm.

Discernment examines that space between what happened and what we conclude it means.

Ask:

What patterns are emerging? Which assumptions survive contact with the evidence? What now deserves to continue, change or be examined more closely?

This matters because development built around the wrong interpretation can make us work harder without addressing the actual problem.

October should therefore produce more than another page of thoughts.

It should leave you with one to three conclusions that the available evidence reasonably supports.

November — Develop

What now needs to become stronger?

Once the situation is clearer, development becomes more purposeful.

If October suggests that the difficulty is not simply personal discipline but weak prioritisation, November is not the month to write another resolution to “work harder”.

It is the month to build or test something better.

That might mean restoring a weekly review, limiting the number of active priorities, strengthening a skill, asking for support, redesigning a process, establishing a boundary or testing a different way of working.

The distinction is important:

Development is about building capability and testing improvement.

It is not yet about making permanent commitments.

In our example, someone might restore a weekly 30-minute priority review for November and limit themselves to three genuinely active priorities at a time. At the end of the month, they can examine whether those changes improved focus and reduced reactive work.

Development also includes subtraction.

Growth does not always require another course, another goal, another habit or another responsibility.

Sometimes the most developmental decision is to remove something that repeatedly consumes capacity without creating sufficient value.

November should leave you with something stronger than you had before: a capability, practice, system, boundary or source of support that has been tested rather than merely intended.

December — Dedicate

What deserves my commitment?

December should not become another month of adding things to an already overloaded life.

For many people, it is one of the busiest and most depleted periods of the year. That makes it a particularly poor time to create an ambitious catalogue of New Year promises.

Dedication should do the opposite.

It should narrow the field.

Having discovered what happened, discerned what it means and tested what needs developing, ask:

What is important enough to carry forward? What will I deliberately stop? What will I protect when competing demands return?

The distinction between November and December is simple:

November asks: What could work better?

December asks: What am I now prepared to stand behind?

Perhaps the November experiment showed that a weekly review genuinely improved focus. December turns that experiment into a protected practice.

Perhaps limiting active priorities worked. Dedication may mean committing to that boundary rather than returning to unlimited work in January.

And perhaps something you tested did not help.

You do not have to carry it forward simply because you started it.

December might result in only two or three commitments.

That is enough.

A meaningful commitment gains strength partly from what we choose not to pursue alongside it.

The practice: one month, one task, one useful output

The BER Reflection should not become another complicated productivity system.

A simple rhythm is enough.

Set aside one focused review during each month — around 30 minutes is sufficient for many people — and capture useful evidence as it arises between reviews.

The method is deliberately light.

Its value is not in how much you write. It is in whether the process helps you see more clearly and act more deliberately.

When reflection stops helping

Reflection has a shadow side.

We can use it to ruminate, justify ourselves, repeatedly reopen the same question or postpone action because we are “still thinking”.

Good reflection does not require endless reflection.

At some point, it should produce movement: a clearer understanding, a better question, an experiment, a boundary, a decision or a commitment.

Otherwise reflection itself can become another form of avoidance.

The purpose is not to remain permanently between experience and action.

It is to improve what happens in that space.

Why this matters beyond the individual

The principle underneath the BER Reflection extends beyond personal development.

Reflective Intelligence is concerned with strengthening the human layer between information, interpretation, judgement and action.

That matters in our personal lives and careers. It matters in leadership and organisations. And it matters increasingly as artificial intelligence becomes part of how information, predictions and recommendations reach us.

AI can generate outputs at extraordinary speed.

Information is not action.
AI output is not authority.
Confidence is not certainty.

Someone still has to determine what the information means, whether the evidence is sufficient, what uncertainty remains, which boundaries apply and who remains accountable for what happens next.

At an organisational level, the same Discover → Discern → Develop → Dedicate sequence also structures the wider RILayer implementation path.

RILayer is the organisation-facing Reflective Intelligence infrastructure being developed to make evidence, assumptions, readiness, governance risk, boundaries and human accountability more visible before consequential action proceeds.

Its current proof-of-concept work focuses particularly on Discern: examining the judgement conditions before action rather than treating an AI or system output as the decision itself.

The setting is very different from a personal year-end reflection.

The underlying discipline is nevertheless familiar:

better action depends on creating better conditions for judgement before we proceed.

Your four-month invitation

You do not have to wait until 31 December to work out what the year has taught you.

And you do not need 1 January before you begin responding to it.

Use September to Discover what happened.

Use October to Discern what it means.

Use November to Develop what needs to become stronger.

Use December to Dedicate yourself to the few things worth carrying forward.

Don’t just end the year.

Learn from it.

Because the real value of reflection is not how thoroughly we can explain yesterday.

It is whether what we learn improves the judgement we carry into tomorrow.

Continue your reflection

Reflect with SCOPE →

Use SCOPE to organise facts, assumptions, options and evidence when you need a clearer view before deciding what to do next.

About the author

Sam Soyombo

Founder and Ecosystem Architect

Sam writes about career development, reflective capability, learning, human transition and the development of Reflective Intelligence for responsible human judgement.

About Sam →More articles →