How PILLAR works

A clear process, so there are no surprises.

Here is exactly what happens during a PILLAR Assessment — what we ask, who we talk to, how long it takes, and what you receive at the end.

What PILLAR answers

Four questions every engagement ends up answering.

Many consultants jump straight to a solution. We separate understanding the problem from deciding what to do about it.

01

What is actually happening?

A shared understanding of the current state — what leadership sees and what staff experience.

02

Why is it happening?

Root causes, not symptoms. Most problems that look like technology problems are not.

03

What does it cost or threaten?

The impact on time, money, people, compliance, and mission.

04

What should happen next?

A prioritized roadmap you can act on and explain to your board.

Where we look

Process. Infrastructure. Leadership alignment.

We look at each through the same lens: what the evidence shows, who it affects, and what it costs.

Process

How work actually moves through your organization — the handoffs, workarounds, and duplicated steps that quietly consume staff time.

Infrastructure

The platforms, data, and integrations your team depends on — what's working, what overlaps, and what's no longer serving you.

Leadership alignment

Whether your systems reflect leadership's goals — so technology decisions are grounded in organizational needs, not vendor pitches.

The timeline

About 30 days. Up to 45 for larger organizations.

A typical engagement, week by week.

  1. Week 1

    Onboarding and executive kickoff

    A kickoff conversation with your executive sponsor and operational lead. We agree on what success looks like, who we should hear from, and which documents and system information we need.

  2. Weeks 2–3

    Listening and review

    Conversations with the people who actually do the work, and working sessions with the owners of your systems. This is where we find the workarounds and shadow processes no diagram shows.

  3. Week 4

    Analysis and technical report

    We turn what we heard and observed into findings, each tied to evidence, and assemble the detailed technical record.

  4. Week 5

    Internal review and executive presentation

    Our team challenges its own conclusions before you see them, then builds the leadership presentation around your mission and your people.

  5. Week 6

    Findings and decision workshop

    We present the findings live to your leadership, then work through priorities together so you leave with a roadmap and a decision path.

Your time

Meetings only where a conversation makes the difference.

We use documents and tools to share information. We save your calendar for interpretation, judgment, and decisions.

Executive kickoff

About 60 minutes

Executive sponsor, operational lead

Agree on outcomes, stakeholders, scope, and concerns

Stakeholder conversations

30–45 minutes each

Selected staff who use your systems

Hear how the work really gets done

Technical sessions

60–90 minutes

Owners of your systems and data

Validate systems and dependencies

Midpoint check-in

20–30 minutes

Operational lead

Resolve anything still missing — only if needed

Findings presentation

75–90 minutes

Leadership and key stakeholders

Present findings and build shared understanding

Decision workshop

45–60 minutes

Decision-makers

Prioritize the response and the path forward

How findings are presented

Every major finding follows the same four parts.

We begin with your mission and what we heard — not thirty technical deficiencies. Each finding connects a technical condition to the people it affects.

01 — Observation

Staff maintain three parallel spreadsheets because the CRM can't produce a report anyone trusts.

02 — Human impact

People spend hours reconciling information and are never sure which version is correct.

03 — Organizational consequence

Reporting to funders is delayed, and leadership decisions rest on numbers nobody is confident in.

04 — Recommendation

Establish one governed source of truth and retire the duplicate reconciliation work.

An illustrative example, not a client finding.

After PILLAR

You decide what happens next.

The roadmap is yours. Some organizations ask Abide to help carry it out; others take it to their own team or another partner.

Elliott Godwin, founder of Abide

Elliott Godwin

Founder, Abide

Abide is a small team. When you reach out, you'll hear from a real person who will listen before recommending anything.

Meet the people behind Abide →

Start with a conversation.

Book a free 30-minute discovery call. We'll listen first, then tell you honestly whether PILLAR is the right next step.

Schedule a 30-minute discovery call
Book a free 30-minute call