Bart Groenendal · Independent advisory for engineering leadership

The symptoms are visible.
The cause often is not.

VerdantDale is my independent advisory practice for CTOs, VPs of Engineering and engineering leaders facing difficult operational and organisational questions. I help you see the situation clearly enough to make the decision. Independent judgement, not implementation.

Remote, worldwide · English & Dutch

Get in touch See engagements

When it helps

A difficult situation needs an independent view.

The symptoms may be technical, but the cause can sit between teams, ownership and business constraints. I help leadership understand how those pieces interact, especially when the available explanations don't add up.

Incidents recur despite repeated fixes
Ownership is unclear until something breaks
Delivery stalls at team or system boundaries
Product and platform priorities pull apart
Regulatory obligations such as NIS2 strain the operating model
A consequential decision needs an outside challenge

Engagements

A clear question. A useful outcome.

Each engagement starts from one agreed question and ends with what you need to make a decision. The scope follows the question.

A concrete place to start

Async incident record review

Fixed scope and fixed price, agreed before work begins. About two weeks from receiving the material.

For engineering leaders working under NIS2. A significant incident is reported in phases: an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within one month. The review answers one question: could you reconstruct and report a real incident in time, from what you actually record?

The work: You share two or three past incident reports or post-mortems, and exports of your catalogue and ownership data. I trace each incident through five timestamps, from start to root cause resolved, and five lookups, from owner to who would make the reporting call. Each is marked recorded at the time, reconstructed afterwards, or unknown. No interviews needed.

You leave with: A short written assessment of where the chain breaks against each deadline, and the decisions to take. The same gaps lengthen ordinary incidents, so the findings are useful beyond reporting. Optional walkthrough.

I do not determine whether an organisation falls under NIS2 or whether an incident was legally reportable. I show whether its own record could support that decision, and the report, in time.

Discuss a record review

Broader assessment

Availability is limited and scheduled individually.

For an operational or organisational problem that spans several teams, systems or suppliers, where no single symptom explains the whole situation.

The work: I examine the relevant material and hold selected conversations with leaders and operators. I look at ownership, dependencies, escalation and the operating model, and how work actually runs across them.

You leave with: A structured view of how the problem arises, the gaps and risks that matter, and prioritised decisions with explicit trade-offs.

Discuss a broader assessment

Decision challenge

For a consequential decision before you commit: platform direction, an ownership or operating model change, resilience investment or the operational use of AI.

The work: I challenge the assumptions, evidence and options against your technical, organisational and commercial constraints.

You leave with: Explicit risks and trade-offs, and a recommendation or decision framework leadership can defend.

Discuss a decision challenge

Different problem or scope?

If your question does not fit the engagements above, we can scope the work around it, even if you are not yet sure what it needs.

Tell me what you're working through

How I work

Scoped work, little overhead.

Work is async by default. You share material, I read it, and we meet only when a conversation adds something the material cannot.

Intake

You share the situation, the question and any material. We agree the scope and commercial terms before work begins.

Review

I examine the material and, where the work needs it, speak with leaders or operators. I test the explanations on offer against how things work in practice.

Close

You get a clear assessment and priorities for what comes next, with a walkthrough if useful. The output supports decisions, not documentation for its own sake.

No standing cadence by default, and no incentive to extend the engagement beyond the question we agreed to address.

About Bart

Experience across different kinds of complexity.

I'm Bart Groenendal. I've spent roughly twenty years in technology environments across government and public infrastructure, fintech and core banking, and large-scale consumer technology and services.

The organisations and constraints differed, but each required me to understand unfamiliar businesses and technical environments quickly: how work flows, where responsibility sits, and how reliability, regulation and commercial realities shape the choices available.

My recent work has been product ownership of software catalogue, ownership, service health and incident learning, in a landscape of more than 100,000 software systems. That experience informs my judgement at VerdantDale.

Tell me what you're seeing

You don't need a diagnosis or a defined scope. Tell me what you're working through and what you need to decide.

I read enquiries personally and normally respond within a few business days. If a short call helps establish fit, I'll suggest one. Availability depends on scope and current commitments.

Prefer email?
Or LinkedIn.

Thank you. I read enquiries personally and normally respond within a few business days. Availability for an engagement depends on scope and current commitments.

The symptoms are visible. The cause often is not.