How PILLAR works
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
Many consultants jump straight to a solution. We separate understanding the problem from deciding what to do about it.
01
A shared understanding of the current state — what leadership sees and what staff experience.
02
Root causes, not symptoms. Most problems that look like technology problems are not.
03
The impact on time, money, people, compliance, and mission.
04
A prioritized roadmap you can act on and explain to your board.
Where we look
We look at each through the same lens: what the evidence shows, who it affects, and what it costs.
How work actually moves through your organization — the handoffs, workarounds, and duplicated steps that quietly consume staff time.
The platforms, data, and integrations your team depends on — what's working, what overlaps, and what's no longer serving you.
Whether your systems reflect leadership's goals — so technology decisions are grounded in organizational needs, not vendor pitches.
The timeline
A typical engagement, week by week.
Week 1
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.
Weeks 2–3
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.
Week 4
We turn what we heard and observed into findings, each tied to evidence, and assemble the detailed technical record.
Week 5
Our team challenges its own conclusions before you see them, then builds the leadership presentation around your mission and your people.
Week 6
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
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
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
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, 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 →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