The biggest challenge after setting up Pirros is getting your team to change their habits. Most firms report that senior staff default to digging through old project files even after Pirros is fully loaded. This article covers what works.
Why Adoption Stalls
Common reasons teams revert to old workflows:
They're mid-project and don't want to learn something new under deadline pressure
They don't know Pirros has the content they need
The old method (asking a colleague or opening past models) still works — it's slower, but familiar
They tried Pirros once and didn't find what they needed (possibly because projects hadn't been uploaded yet)
Strategies That Work
1. Remove the old path
If your team can still access details the old way (shared drive folders, template files), they will. Consider moving or archiving those legacy folders once the same content is in Pirros. When the old path disappears, Pirros becomes the path of least resistance.
2. Time your rollout with project phases
Teams in SD or early DD aren't pulling many details. Roll out training and push adoption when teams enter CD phase — that's when they need details most and the time savings are immediately felt.
3. Designate a Pirros champion
Identify one person per team or office who becomes the go-to for Pirros questions. This person should be comfortable with the platform and willing to help colleagues during the transition.
4. Treat library development as a project
The most successful firms assign dedicated hours for library work — uploading projects, tagging details, creating firm stashes. Set milestones and track progress like any other project deliverable.
5. Use analytics to show value
Share download statistics with your team. When people see that 200 details were downloaded last month, it validates that the platform is being used and that they're missing out by not participating.
6. Build firm stashes for common project types
Firm stashes give new project teams a one-click starting point. When the first thing a PM or PA does on a new project is download the "Healthcare Starter" stash, Pirros becomes embedded in the project workflow.
Training Recommendations
Initial training: 30-minute session covering search, download, and stashing — the three things members do daily
Refresh training: After 2-3 months, run a 15-minute session showing what's new in the library and highlighting usage stats
New hire onboarding: Add Pirros to your new employee checklist — account setup, plugin install, and a 10-minute walkthrough
Frequently Asked Questions
Q: What's a realistic adoption timeline?
A: Most firms see 30-40% active usage within the first month after training. With the strategies above, this typically grows to 60-80% within 3-6 months.
Q: How do I track who's using Pirros?
A: Go to Management → Analytics to see download counts by user, team, and project. This shows who's actively using the platform and who might need a nudge.
Q: Some team members are resistant to any new technology. What do I do?
A: Focus on the path-of-least-resistance strategy — if Pirros is faster than the alternative, most people adopt naturally. For holdouts, pair them with the Pirros champion and show them a live search for a detail they recently spent time finding the old way.