Driving user adoption after PSA go-live: the first 90 days

PSA user adoption is decided in the first 90 days after go-live, not at launch. The playbook has three phases: lock the weekly time-entry habit through manager approvals (days 1–30), make the system the only accepted source of reports and answers (days 31–60), then expand into resource planning and financials while proving value against your pre-purchase baseline (days 61–90).

Here is the uncomfortable part: configuring the system was the easy half of the project. Every promise that justified the purchase, utilization visibility, project profitability, resource forecasting, sits on top of one fragile behavior: complete, timely time entry by busy people who have client work to do. If that behavior does not become a habit, the reports are wrong, and wrong reports kill trust faster than any bug.

The dip is coming either way. In most PSA rollouts we support at Birdview, time-entry compliance drops noticeably in weeks 2–3 after go-live. The dip itself is normal. Whether it becomes the new normal is a management decision, and the 90 days after launch are when that decision gets made. This article is the operating manual for those 90 days.

Why adoption sags after go-live

Adoption sags because launch energy fades, enforcement feels like micromanagement so managers avoid it, and the old spreadsheets are still one click away. None of these forces is dramatic. Together they are enough to sink a rollout quietly.

The mechanics follow a pattern. Week one, compliance is high because the tool is new and everyone attended the training. In weeks 2–3, a busy week hits, a proposal deadline or a client escalation, and time entries slip to “I’ll catch up Friday,” then to “I’ll reconstruct it next week.” By week four, the first utilization or budget report comes out wrong because the underlying data is incomplete. Skeptics point at the wrong report as proof the tool failed. That is the death spiral: not dislike of the software, but data-driven distrust caused by the very behavior the skeptics stopped doing.

The stakes are real. Roughly 60% of the firms we talk to in discovery calls have already bought and abandoned at least one project management tool before evaluating a PSA. Most of those abandonments were adoption failures, not product failures. Firms that manage the dip deliberately reach stable compliance within 6–8 weeks; firms that let it settle join the abandonment statistic and go back to spreadsheets with a software invoice attached.

Days 1–30: lock the habit

The first month has exactly one goal: complete weekly time entry from every full user, enforced through the approval workflow. Everything else, dashboards, portfolio views, financials, is secondary until this holds.

Behavioral research backs the timeline. The most cited study on habit formation, Lally et al. (2010) in the European Journal of Social Psychology, found that new behaviors take a median of 66 days to become automatic, with simple daily actions forming faster. Weekly time entry with a fixed deadline sits at the easier end of that range, which is why a disciplined first month usually produces a durable habit by week six.

The weekly approval ritual

Manager approval of time, every week, starting week one, is the single highest-leverage adoption mechanism available to you. Approval creates a natural weekly deadline, surfaces missing entries within days instead of at month-end invoicing, and signals that leadership actually looks at the data. People log time that someone reads. They stop logging time that disappears into a void.

Make the ritual concrete. Pick a fixed approval day, Friday close of business or Monday morning both work. Put a recurring 15-minute block on every approver’s calendar. Define the escalation path for chronic stragglers up front: first a reminder from the approver, then a conversation with their manager, so nobody is improvising discipline in week three.

Make compliance visible

Publish a simple compliance number, the percentage of timesheets submitted on time by team, and review it in a meeting that already exists, your weekly ops or leadership sync. Do not build a shaming wall. A visible, factual, team-level number is enough; teams self-correct when they can see where they stand relative to their peers.

Set the target explicitly. Across the rollouts our implementation team has run, above 90% on-time submission by week six is the threshold where the habit is locked and the downstream reports become trustworthy. Below that, treat adoption as your primary open project.

Reduce friction before adding pressure

Before escalating on any individual, check the friction first. In our experience most “resistance” in month one is actually a workflow problem. Common fixes: switch reconstruction loggers to start/stop timers, enable mobile time entry for field staff and traveling consultants, and pre-assign tasks so people log against the right project without hunting through a list. A person who spends ten minutes finding the right task will stop logging by week three, and no amount of pressure fixes a ten-minute search.

One scoping note that saves goodwill: a typical professional services firm runs 20–60 full users alongside 50–200 collaborators or light users. Collaborators need almost nothing in this phase. They consume status, approve the occasional item, and comment. Do not burn your training capital on people who will never enter a timesheet.

Days 31–60: make it the single source of truth

The habit only holds long-term when the system becomes the only place answers come from. Month two is where leadership behavior, not user behavior, determines the outcome.

Leadership stops accepting sidechannel reports

The forcing function is simple and slightly uncomfortable: from day 31, status updates, utilization questions, and budget checks get answered from the PSA dashboard, live, in the meeting. When a number looks wrong, the response is “fix the data” rather than “send me the spreadsheet version.” The quiet rule that changes everything is if it is not in the system, it did not happen, and it has to apply to the partners and executives first. Prosci’s Best Practices in Change Management research has found active and visible executive sponsorship to be the top contributor to change success in every edition of the study since 1998, and this is what visible sponsorship looks like in practice: leaders using the tool in public, not endorsing it in an email.

Retire the legacy tools on schedule

The spreadsheet freeze date you set during rollout gets honored in this phase. Run legacy trackers in parallel for one full billing cycle at most, then make them read-only. An indefinite parallel run tells the team the new system is optional, and optional systems lose. (The full argument lives in the implementation mistakes guide; the short version is that every week of parallel running doubles the reconciliation work and halves the urgency.)

Watch for shadow trackers reappearing in pockets of the firm. A team quietly rebuilding a spreadsheet is almost never rebellion. It is usually a missing report view, a permission gap, or a workflow the system does not yet cover, in other words, a friction problem wearing a compliance costume. Ask what the spreadsheet does that the system does not, then close that gap.

Announce the first public wins

Month two is when the milestones promised during the sales process start arriving, and they should be marketed internally. The first one-click status report that replaces the monthly Excel assembly ritual. The first invoicing cycle that takes two hours instead of a full day, a milestone worth celebrating loudly given that about half the firms we meet describe month-end invoicing as an all-day job for someone. The first time a resourcing question (“who is free next week for this engagement?”) gets answered live from the capacity view instead of by email survey.

Skeptics do not change their minds in training sessions. They change their minds when they watch a task they hated disappear.

Days 61–90: expand usage and prove the value

With two months of trustworthy time data flowing, month three is when you switch on the capabilities the firm actually bought the PSA for, and close the loop against the baseline that justified the purchase.

Expand in deliberate waves

The sequence that works: time tracking and project management (already live) → resource planning against real actuals → budget vs. actuals and margin reporting → client or guest portal for external visibility. Roll out one wave at a time, 2–3 weeks apart, and give each wave the same treatment as phase one: a named owner, a weekly routine, and a visible metric.

The rationale for the order is data quality, not caution. A resource forecast built on incomplete timesheets is fiction with a chart. Margin reporting on top of missing hours will show phantom profitability and trigger exactly the wrong pricing decisions. Two months of clean actuals is the foundation that makes the advanced features honest.

Measure against the baseline

Pull out the three numbers you captured before purchase: hours per month spent assembling reports, invoicing cycle time, and on-time time-entry percentage. Publish the before-and-after to leadership at day 90. This comparison is the sponsor’s renewal insurance and the system owner’s credibility deposit, and it converts “the tool seems fine” into “the tool returned X hours a month.”

If nobody captured a baseline before purchase, reconstruct what you can now, invoicing time is usually recoverable from calendars and memory, and start the clock for a 90-day forward measurement. �

Institutionalize ownership

Adoption stops being a project when three things become permanent. Name the system owner formally, usually the operations leader who ran the rollout, with the role written into their objectives. Set a monthly tuning cadence for report requests, permission changes, and template updates, because an unmaintained system accumulates friction until people route around it. And fold the PSA into new-hire onboarding from day one, so every future employee meets the system as “how we work here” rather than “the new tool.”

The adoption metrics that matter

Track four numbers, weekly, for the full 90 days: on-time compliance, approval latency, active usage by role, and reporting lag. Together they tell you whether the habit is holding, whether managers are doing their part, and whether the system is actually replacing the old workflow.

The ranges above reflect what our implementation team sees in successful rollouts; validate them against your own firm’s rhythm rather than treating them as physics.

One honest caution: logins are not adoption. A collaborator who checks project status twice a month is fully adopted for their role, and a full user who logs in daily but reconstructs time from memory on Fridays is not. Define adoption per role, then measure against that definition.

Handling holdouts without poisoning the rollout

Separate friction from resistance before acting, because the fix for each is different. Friction, a clumsy view, no mobile entry, unclear task assignment, gets fixed by the system owner, quickly and without ceremony. Genuine resistance gets a private conversation between the person and their manager, anchored on the team’s compliance number, never a public callout. Public shaming turns one holdout into a faction.

The one non-negotiable: senior people are not exempt. A partner who visibly skips time entry licenses everyone below them to do the same, and unwinds three months of habit-building in about two weeks. If the firm’s leaders will not log time, stop the expansion waves and fix that first, because nothing downstream will survive it.

What the 90 days add up to

Phase one locks the time-entry habit through weekly approvals and visible compliance. Phase two makes the system the only source of truth by changing what leadership accepts. Phase three expands into resourcing and financials and proves the return against a baseline. None of it requires an enthusiastic team; it requires a management routine run consistently for one quarter. Adoption is not a personality trait of your firm. It is a set of weekly rituals that either happen or do not.

If you are still evaluating and reading this to de-risk the decision, our guides on the PSA implementation timeline and common implementation mistakes cover the road that leads up to day one. And when you compare vendors, ask specifically what post-go-live support looks like: Birdview’s Path to Success program, for example, pairs new customers with an implementation consultant through exactly this 90-day window, which matters more to the outcome than most feature checkboxes.

FAQ

What is a good time-entry compliance rate? Above 90% of timesheets submitted on time is the working threshold where downstream reports become trustworthy; successful rollouts usually reach it by week six. Chasing 100% is the wrong target, because the last few percent costs more management attention than the data is worth. Track the number weekly by team and treat a sustained drop below 90% as an open problem.

How long does it take a team to adopt a new PSA? Expect the time-entry habit to lock in within 4–6 weeks if weekly approvals run from day one, and expect the system to feel like the firm’s default way of working by roughly day 90. Plan for a compliance dip in weeks 2–3 after go-live; it appears in most rollouts and is manageable when anticipated.

How do you get senior staff to track time? Leadership modeling beats mandates. When partners answer questions from the system in meetings and submit their own time on schedule, compliance below them follows within weeks. The reverse also holds: one visibly exempt senior person licenses the whole firm to slip. Apply the source-of-truth rule to leadership first, then to everyone else.

Should you tie time-entry compliance to performance reviews? Not as a first move. Visibility, weekly approvals, and friction fixes solve most compliance problems without formal consequences, and leading with penalties frames the PSA as surveillance. Reserve performance-review consequences for chronic cases that persist after friction is removed and a direct manager conversation has happened, and apply them consistently across seniority levels.