Findings in this brief are drawn from two decades of fieldwork and data analysis, working alongside dozens of credit unions and watching their operating models evolve through every stage of this arc.
What this brief argues, in six lines.
- 01Every department in a credit union runs projects — Marketing, IT, Lending, Branch Operations, Digital, Risk & Compliance, and HR. Most of it is collaborative. Much of it is recurring. A meaningful slice runs across departments.
- 02How that work is run matures along a predictable four-stage arc: Hands-On Coordination, The Visibility Cliff, Operational Drag, and Project Operations at Enterprise Scale[5][6]. Tooling is the visible symptom at each stage, not the stage itself.
- 03Each stage has its own breaking point. In Tier 1, the work is invisible to anyone except the person running it. In Tier 2, the across-department view goes dark just as each department gets sharper on its own work. In Tier 3, time spent coordinating overtakes time spent on the work itself. In Tier 4, the board and the NCUA expect board-grade program reporting. The failure mode changes in kind at every threshold from under $100M to $10B+ in assets[5][6].
- 04The expensive failure isn't the work itself. It's the coordination around it. Programs slip on handoffs nobody could see. Exam and audit prep gets rebuilt from memory every year. Approvals sit in email. Capacity is committed on gut feel. Partners and examiners are bolted on through workarounds.
- 05Credit unions that install the right operating layer ahead of their next inflection point take coordination time off every department, free leadership from rebuilding status, and de-risk whatever comes next. Whether that's merger integration, core modernization, digital expansion, or scaling into the next asset tier.
- 06Use the tier-by-tier framework to locate your credit union, the interactive explorer to see the challenges and fixes at your stage, and the self-audit to benchmark your operating maturity against peers at your size.
Project work runs in every department. How it's run evolves on a predictable arc.
Every function runs projects. Marketing runs campaigns and product launches. IT runs upgrades and core or digital rollouts. Lending runs product launches and rate changes. Branch Operations runs branch openings, refreshes, and member-experience programs. Digital runs app releases and fintech work. Risk & Compliance runs exam prep and BSA/AML reviews. HR runs hiring waves and annual training. Most of this work is collaborative. Much of it is recurring. A meaningful slice runs across departments[1][3].
How that work is run matures along a predictable four-stage arc. Early on, personal relationships hold everything together. As the credit union grows, each department gets sharper on its own work — and the view across departments goes dark. Eventually the time spent coordinating across functions overtakes the time spent on the work itself, and a shared project layer becomes the only way through[5][6]. This brief maps the four stages and the failure mode that breaks each one.
Departments outgrow their tools but stay on them out of inertia, layering spreadsheets and email back on top to fill the gaps. The work gets done, but it doesn't land on time, on budget, or with the cross-functional coordination needed to compound across the credit union.
Four tiers of operating maturity, by asset size.
Each tier is defined less by asset size than by how the average department is operating — and the inflection point that breaks it. Asset size is the cleanest proxy because regulatory burden, system complexity, and product breadth all scale with it.
Hands-On Coordination
Personal relationships hold project work together across every department.
Project work in every function, Marketing, IT, Lending, Branch Operations, Digital, Risk & Compliance, HR, runs on personal coordination. Department leads know each other, know the work, and hold the plan in their heads. The visible artifacts are spreadsheets, decks, and email threads, but the operating model is one person remembering what is in flight.
When a single person being out of office stalls work in three different departments because the project lives in their inbox.
The Visibility Cliff
Departmental visibility is real. Cross-functional visibility has collapsed.
Each function has tightened its own operating model and can answer for its own work. The cross-functional layer has gone dark. Leadership can see inside any single department but cannot see across them, and cross-functional programs have no shared owner, plan, or status. The symptom is a sprawl of generic task tools, one per department; the underlying condition is that no shared operating layer exists.
When the leadership team realizes it is paying for six different project tools and still cannot answer what is in flight across the credit union.
Operational Drag
A PMO exists. Cross-functional coordination is now the constraint on strategic work.
An enterprise PMO or transformation office stands up, often as a small team reporting to the COO or CIO. Most departments have moved past spreadsheets and are running their own task tools well. The new problem is the cost of coordinating across them, programs that touch four or five functions take longer than the work itself warrants.
When the cost of coordinating across departmental tools exceeds the cost of standardizing on a shared one.
Project Operations at Enterprise Scale
Project work runs as an instrumented operating system. Reporting is board- and NCUA-grade.
Project work is run on a shared enterprise platform that every department uses for collaborative work, with deep-domain systems (core, LOS, digital banking, CRM, BSA/AML, card platforms) feeding into it. The PMO has standing governance, capital allocation runs on portfolio data, and reporting on strategic programs is a standing input to ALCO, the board, and the NCUA exam.
When the credit union crosses $10B and falls under direct CFPB supervision, every strategic execution becomes a board-level event and reporting on the project portfolio is a standing input to board and regulator materials.
Find your stage. See the challenges, the impact, and what fixes them.
Drag the slider to your asset size. The rest of this section reflects the project-management challenges most likely to be hurting your departments right now, with the corporate and team-level impact, and how a platform like Workzone resolves each one.
The Visibility Cliff
Departmental visibility is real. Cross-functional visibility has collapsed.
Between $100M and $1B in assets (typically 3–15 branches, 25–150 employees), this is the most common stuck point. Crossing $500M triggers a required external audit and tighter ALM expectations. Departments have outgrown spreadsheets and each picked a tool that fits the depth of one function: Marketing on one task tool, IT in Jira or ServiceNow, Lending in a CRM workflow, Digital on a product board, Compliance on a SharePoint list, HR in an LMS workflow. The within-function picture is sharper. The across-function picture is worse than it was at Tier 1, because the tools don't talk to each other and no two teams share a vocabulary. Leadership reporting becomes a manual reconciliation across tools, and cross-functional programs slip on handoffs no one can see.
Pick the function you care about most. The challenges below filter to the ones that department feels first. Pick All to see the full org-wide view.
Six different tools, no shared view
Each function picked the task tool that fit its own work, and within that scope each one is fine. The portfolio question, what is in flight across the credit union, who owns it, what is at risk, has no answer because no tool was set up to answer it.
Leadership can ask any single department what is on its plate, but cannot see the whole picture without a manual rollup. Strategic-plan tracking becomes a quarterly heroic exercise.
Cross-functional program owners spend half their week translating between tools and rebuilding the cross-tool view in Excel.
Land on a shared work-management layer that every department uses for collaborative project work, and keep specialized deep-domain systems only where they are genuinely needed for that function's deepest work.
Workzone gives every function the same project workspace with department-tailored views, and rolls everything up into one portfolio leadership can actually use.
Score your operating maturity in 2 minutes.
Set your asset size, answer 12 yes-or-no questions distilled from the tier challenges above, and get a maturity score, your tier label, and the three highest-impact gaps to close first.
500 million in assets · Tier 2 · The Visibility Cliff
Mark each statement yes if it is true today, no if it is not.
- 01Critical at T2
Every department (Marketing, IT, Lending, Branch Operations, Digital, Risk & Compliance, HR) runs collaborative project work in one shared platform, not its own private spreadsheet or task tool.
- 02Critical at T2
Leadership has one portfolio view of every active project across departments, with sponsors, owners, status, and dependencies.
- 03Critical at T1
Requests for internal service functions (IT, Marketing, Digital, Compliance) come in through one front door with a structured brief, not Slack DMs and email.
- 04Critical at T1
Recurring programs (NCUA exam prep, BSA/AML reviews, rate-sheet updates, disclosure refreshes, branch openings, annual training, onboarding) run from cross-functional templates, not memory.
- 05Critical at T2
Cross-functional projects (product launches, core conversions, digital migrations, branch expansion, merger integration) have one shared plan with a named owner per contributing function.
- 06Critical at T1
Reviews and approvals (vendor contracts, lending policy changes, marketing creative, member disclosures, procedure updates) flow through a structured workflow with online proofing and a per-version audit trail, not email.
- 07Critical at T1
Project files (creative, rate sheets, disclosures, lending policies, branch playbooks, vendor contracts, plans) live attached to the project with versioning, not scattered across drives.
- 08Critical at T2
External partners (agencies, core implementation teams, digital-banking vendors, fintech partners, external auditors, examiners, outside counsel) work in the same project workspace as internal teams, with controlled access.
- 09Critical at T2
Department heads can show committed work versus team capacity in real time, by person and by function.
- 10Critical at T2
Leadership can see, on demand, which projects are on track, at risk, or slipping, with the late milestones, blocked tasks, and overdue approvals behind the status.
- 11Critical at T2
Dependencies between projects (a core cutover blocking a digital release, a vendor delivery blocking a product launch, a compliance ruling blocking a campaign) are tracked in the system, not in a program manager's head.
- 12Critical at T2
A new employee in any department can land and contribute in their first two weeks because templates, owners, and current state are documented in the system.
- 13Critical at T3
When a project misses deadlines or budget, we can clearly identify the root cause of the variance.
- 14Critical at T3
We can accurately forecast project timelines, budgets, and resource needs before issues occur.
The operating layer that resolves these challenges.
Most of the failures above are not strategy failures. They are not depth-of-function failures. They are coordination failures at the project layer that runs across departments. Tools that don't talk to each other. Recurring exam and audit prep rebuilt from memory. Approvals stuck in email. Capacity committed on gut feel. External partners and examiners bolted on through workarounds.
Project management software does not replace your core, LOS, digital-banking platform, CRM, BSA/AML, or card platform — and should not try to. It sits alongside them and runs the collaborative project work that wraps around them. The capabilities below are what platforms like Workzone deliver, mapped to the tier-by-tier challenges above[5][6].
A shared project platform every department can use
One platform for collaborative project work across every function, with department-tailored views inside it. Deep-domain systems stay where they belong.
A single front door for project requests
Standardized intake forms with required briefs, automatic triage, and a status link the requester can check, for every internal service function.
Templated playbooks for recurring cross-functional work
Reusable cross-functional templates with named function owners, dependency wiring, and pre-set due-date offsets for every program that runs more than once.
Portfolio visibility across every department
Live portfolio view by department, sponsor, function, and program. The board view becomes a saved query rather than a quarterly reconstruction.
Online proofing and structured approval workflows
Sequenced reviews with online proofing, pinned markups on the asset itself, named approvers, deadlines, attestations, and a permanent audit trail of every version.
Capacity and resource planning
A forward view of committed work versus capacity by person and by function, so commitment conversations start from data.
Controlled external collaboration
Permissioned access for external partners so their work shows up in the same portfolio view as in-house work, with the same proofing and approval workflow.
Roll-up reporting across the portfolio
Standardized program status, milestones, and risks that aggregate from project to portfolio. Domain KPIs continue to come from the core, LOS, digital banking, CRM, and BSA/AML systems.
Why we publish on credit unions.
Workzone is project management software built for regulated, multi-stakeholder organizations, Marketing, IT, PMO, Operations, Compliance, and HR teams running collaborative project work side by side. We have more than 23 years of real-world deployment experience and a 7-year average customer lifetime, focused on multi-site, multi-stakeholder organizations where work has to land consistently across many functions and many locations.
Credit unions are one of the categories where that focus matters most. These organizations have real cross-functional complexity, branch-level autonomy, an aggressive merger and digital-transformation cadence, and standing regulatory reporting pressure all running through every department's project work. Alongside, not inside, the deep-domain systems each function depends on (core, LOS, digital banking, CRM, BSA/AML).
We publish briefs like this one because the project-management conversation is one of the highest-leverage ones a credit union leader can have, and it is rarely had with the specificity it deserves.
See what an org-wide project layer looks like in Workzone.
Book a 30-minute walkthrough with a Workzone specialist. We'll map the framework above to your current tier and show you how Marketing, IT, Lending, Branch Operations, Digital, and PMO teams at other credit unions run project work side by side in one shared platform.
"Our Credit Union, BCU, is very purpose-driven, and everything we do goes back to that purpose. As a result, we like to work with purpose-driven organizations that know financial institutions really well. Most platforms try to be everything to everyone. That's why we love that Workzone is focused on specific industries like credit unions. It's easy for us to align with their vision and see where we fit when it comes to their focus on mission-critical industries."
Sources.
- [1]Credit Union National Association (CUNA, now America's Credit Unions): Industry trends and operating benchmarks. https://www.americascreditunions.org/
- [2]NCUA: Credit Union and Corporate Call Report Data and supervisory priorities. https://www.ncua.gov/analysis/credit-union-corporate-call-report-data
- [3]Filene Research Institute: Credit union strategy, operations, and member-experience research. https://filene.org/
- [4]Callahan & Associates: Credit union performance and merger trend reporting. https://www.callahan.com/
- [5]Project Management Institute (PMI): Pulse of the Profession on portfolio and program management practices. https://www.pmi.org/learning/library
- [6]Gartner: Collaborative work management and strategic portfolio management research. https://www.gartner.com/en/information-technology/insights/program-portfolio-management