When Agencies Compare Notes, Everyone Wins
A handful of government professionals recently shared how they’re tackling different problems with the same platform.
Craig Slack manages a large Idaho Health & Welfare environment supporting more than 3,000 users.
Cassie Lint leads Laserfiche strategy for the Idaho Department of Corrections, with a focus on training and rollout.
Scott Rice works at the Idaho Office of Information Technology Services (ITS), focused on onboarding agencies, shared infrastructure, and long-term stability.
Different roles, same shared question: what does it take to get staff genuinely using a system built to make their day easier? The answers were surprisingly consistent.
Three government agencies. One shared platform. A lot of hard-won wins worth borrowing. IT and records leaders across state government recently compared notes on what’s actually getting staff to embrace a new system instead of quietly working around it. The short version: it’s not about the software. It’s about training people by role, asking why a step exists before automating it, and giving every new request a clear owner for the “why.” Here’s what’s working, straight from the people making it happen. Get more good days done.
Beyond Go-Live: What Laserfiche Adoption Looks Like
Laserfiche adoption is the process of getting staff across departments to consistently use a shared platform for documents, forms, and approvals instead of falling back on email, spreadsheets, or department-specific tools. Strong adoption depends less on the technology itself and more on training, clear ownership, and processes worth automating. Agencies that treat it as a people-first effort, not just a software rollout, see faster and more durable results.
Why It Matters for Government Agencies
For public-sector teams, strong adoption means every division gets the benefit of automation, not just the ones with the most enthusiastic champion. It supports consistent service for citizens, stronger audit readiness, and less pressure on the one person who might otherwise end up training everyone alone. Agencies that get adoption right tend to see requests come to them, instead of having to chase down use cases department by department.
Agency-Wide Momentum
Craig Slack shared a decision that changed everything for his team: purchasing enough licenses to give every employee access, rather than charging departments per project. Removing that cost barrier made it easy for divisions to say yes. His team then built a cross-department approval framework touching close to a dozen processes, delivered in about five weeks. The result reached across thirteen divisions, and the dynamic flipped: instead of the Laserfiche team pitching use cases, divisions started coming to them.
Leadership continuity was another bright spot. A previous director had championed the framework for the transparency it gave into staff work and approvals. When leadership changed, the process needed only minor adjustments to keep running, a strong sign the design was built to last well beyond any one champion.
Role-Based Training Is Paying Off
No one has time to sit through training they don’t need. Cassie Lint is building role-based training programs instead of a single generic course for everyone. Staff can self-serve based on what they actually need to do, which cuts down on one-on-one support requests and keeps everyone working from the same playbook. It’s a simple shift with a big payoff: the training load moves from one stretched-thin administrator to a system that scales naturally as the agency grows.
Asking "Why" First Is Making Automation Stick
When a new request comes in, these leaders agree the first questions should never be about form fields or workflow steps. Start with what problem the team is actually trying to solve, and what’s currently causing pain: rework, delays, too many disconnected systems. One agency requires every new project to have a sponsor, someone inside the department responsible for explaining the impact to staff. Training and technical support come from the Laserfiche team, but the message about why the change matters lands best coming from someone staff already trust.
Migrations Are a Team Effort
You don’t have to do it all with IT bandwidth alone. Several of these agencies had already migrated off legacy systems, including older document management platforms and shared network drives, and found the transition more manageable than expected. In most cases, legacy systems were simply retired once the new process was in place, which simplified things considerably. For agencies with limited IT bandwidth, support typically works like this: Laserfiche is the platform, MCCi is the solution provider, and for state-contract agencies, support usually starts with internal IT before escalating. MCCi also handles migration and project work directly when agencies need extra hands.
Migrations Are a Team Effort
Several of these agencies had already migrated off legacy systems, including older document management platforms and shared network drives, and found the transition more manageable than expected. In most cases, legacy systems were simply retired once the new process was in place, which simplified things considerably. For agencies with limited IT bandwidth, support typically works like this: Laserfiche is the platform, MCCi is the solution provider, and for state-contract agencies, support usually starts with internal IT before escalating. MCCi also handles standalone migration and project work directly when agencies need extra hands.
The Takeaway for Other Agencies
None of these wins came from a feature launch. They came from a licensing decision that removed friction, training built around real roles, a habit of questioning inherited process, and a clear owner for every new request’s “why.” Agencies weighing a new rollout, or looking to get more out of an existing one, can start in the same place these leaders did: ask what problem you’re solving before you ask what form you need.