A leasing team can understand why a process needs to change and still hesitate to use it. The new workflow may duplicate existing records, make a busy shift harder to manage or leave experienced staff unsure which decisions they can still make. Calling that reaction “resistance” too early can hide information the company needs.
To understand why leasing teams resist process changes, look at the cost of the change from their side of the desk. Then make the purpose, responsibilities and evidence of success clear enough that staff can judge whether the new process actually helps.
Identify the objection behind the behavior
A colleague who keeps using an old spreadsheet may distrust the new system, lack training or know about a problem that the project owner has not seen. Those situations require different responses.
| What you hear or observe | What to investigate | Useful response |
|---|---|---|
| “We already enter this information elsewhere.” | Duplicate records and integration gaps | Remove redundant entry or explain the distinct purpose of each record |
| “This will slow down showings.” | The proposed workflow during peak volume | Rehearse a busy shift and simplify the steps that add no value |
| Staff wait for approval on routine choices | Whether the change removed familiar decision authority | Write down what staff can decide and which exceptions need review |
| One experienced colleague avoids the new system | Usability, confidence or a legitimate exception | Observe a real task and resolve the specific obstacle |
| Everyone agrees in meetings but adoption stays low | Whether disagreement feels safe and managers follow the process | Ask privately for concerns and apply the process consistently yourself |
A justified objection does not mean every preference controls the final design. The leader still decides. The difference is that the decision responds to actual work instead of assuming reluctance is a personality problem.
Work through one complete leasing change
Consider this illustrative company. Its leasing team receives inquiries through a shared inbox and listing platforms, but each person keeps a private follow-up list. During absences, colleagues cannot easily see who promised a callback. The proposed change is one shared inquiry record with an assigned next action and due time.
The aim is specific: make inquiry handoffs visible without increasing duplicate data entry. The leasing manager owns the decision. Two leasing colleagues help design and test the workflow, and the operations manager resolves system-access issues. A Remote Team Member (RTM) working a later shift participates because they will receive many of the handoffs.
Capture the suggestion and the concern together
Use a shared idea log with the problem, example, proposed change, affected roles, expected benefit and decision status. For this example, a maintenance coordinator adds a related concern: prospects sometimes ask about unresolved repairs, and leasing staff do not know which property-readiness information is approved for sharing.
That suggestion belongs in the same review because it affects inquiry accuracy. The team adds a link to the approved readiness record instead of asking leasing staff to copy maintenance details into another spreadsheet.
Review the log at a predictable interval and close the loop on every idea. “Deferred until the listing integration is reviewed” is a useful status if it has a reason and a review date. An idea parking lot that never receives decisions will soon stop receiving ideas.
Show the before-and-after workflow
| Stage | Current workflow | Proposed workflow |
|---|---|---|
| Inquiry received | Staff member replies and may add a private reminder | Staff member checks the shared record and records ownership |
| Missing information | Question sits in email | Next action identifies the missing fact and who will obtain it |
| End of shift | Colleague may forward an email thread | Open commitment includes responsible person, due time and acknowledgement |
| Property-readiness question | Staff ask several people or repeat an old answer | Staff consult the approved record and escalate uncertainty |
| Follow-up complete | Private reminder is deleted | Outcome is recorded and the next action is updated or closed |
The company should also specify what the system does not decide. Application approvals, accommodation requests and changes to approved terms continue through the existing authorized process.
Test the process under realistic conditions
Before live use, give each participating colleague two fictional inquiries and one changed fact. Can they find the right record, identify the next action and hand it over without a manager explaining each field? If not, revise the design or training before widening the rollout.
For the illustrative pilot, choose one defined group of listings and a limited period with enough inquiry volume to expose normal handoffs. Record the scope and make sure all shifts know which records belong in the pilot. Do not leave the same inquiry partly managed in two systems.
Agree on success and stopping rules in advance. Review missing next actions, missed commitments, duplicate messages and the time required to record an inquiry.
Stop or narrow the pilot if:
- Messages are sent to the wrong person.
- Important data becomes inaccessible.
- Records are lost.
Protect service continuity while the system problem is resolved.
Use a small baseline sample from before the change. Suppose 7 of 40 sampled open inquiries lack a clear next action. That is 17.5%. If the pilot sample has 2 of 40, the observed proportion is 5%. These hypothetical figures illustrate the calculation; they do not prove the process caused an improvement. Compare similar inquiry types and shifts, and inspect message quality as well as missing fields.
Suppose average recording time rises from 90 seconds to two minutes per inquiry, adding 20 minutes across the 40 cases. In those same comparable samples, missed commitments fall from four to one and duplicate contacts from three to one. A work log shows follow-up and correction time falling from 40 to 30 minutes, counting each activity once even when problems overlap. Recording plus that follow-up work therefore rises from 100 to 110 minutes; fewer blank fields alone have not saved time. The remaining missed commitment occurs during the busiest shift. The manager keeps the pilot limited until a retest shows that the team can meet peak-shift commitments with an acceptable total effort.
Explain the decision and train for the exceptions
At the review, ask staff where the process helped and where it created work. Look at records together rather than relying only on whether people liked the tool. A useful decision could be to keep shared ownership while removing a field that duplicates the property system.
Tell the team what is being adopted, what changed because of their feedback and when the old process ends. Keep necessary historic records accessible under your retention rules. Assign one owner for the current procedure so conflicting copies do not continue circulating.
Training should include the awkward cases: two staff replying at once, an inquiry returning after closure, a colleague going off shift before a promised callback, and a message that needs an authorized decision. People need to practice the situations that previously made their private workaround attractive.
The remote-team playbook provides a place to record the resulting ownership and handoff agreement.
Keep staff involved after adoption
Recognize the contribution accurately. For example, thank the colleague whose readiness-record suggestion removed unnecessary copying. Do not claim they transformed the business if the evidence only shows a cleaner handoff.
Check adoption through sampled work and conversations. If the old spreadsheet returns, investigate what need it serves. It may signal a training problem, a broken field or an exception the official process never addressed.
Leaders also need to use the agreed process. Asking for updates through private messages while insisting everyone else maintain shared records teaches the team that the documented workflow is optional.
When several departments disagree about ownership or decision authority, a tool rollout alone may not resolve it. BetterTeam Consulting can help you clarify how the work should operate before asking the team to adopt another change.
