Retiring the old process: where conventional and progressive meet
How conventional and progressive colleagues can replace a familiar process without keeping two permanent versions of the work.
Conventional and progressive colleagues can make a transition workable by agreeing which function of the old process the new one must preserve. That needs to be followed by a decision about what stops. Simply adding a new workflow leaves two versions running alongside each other, with no shared understanding of which result takes precedence.
Keep the useful function, reconsider the form
Conventional and progressive are positions on the same guide row about ideas and change. A conventional person may prefer familiar, practical approaches. That grounded perspective can reveal the small actions that keep work from falling through the gaps. Its possible pitfall is treating the existing format as indispensable without explaining what it protects.
A progressive person may see possibilities beyond the current arrangement. An inventive approach can challenge why an awkward step exists instead of merely speeding it up. Its possible pitfall is counting an appealing design as a replacement before anyone knows how it handles unusual cases.
The introductory articles on introducing change with a conventional person and making strategy with a progressive person address each preference separately. Here the question is how to retire a process together. Both colleagues may understand the old and new approaches. Preferences establish neither expertise nor authority to approve a change.
Two lists, two apparently correct answers
A maintenance team records repair requests on a paper board. A shared digital list is proposed so staff at another location can see progress. In this fictional example, the board stays in use during the first week. By Friday, the screen shows fourteen open requests and the board shows eleven.
From a conventional perspective, a reasonable question is why the board should go: it gives an immediate overview during the morning round. That is a useful function. Yet returning to paper alone leaves the other location without the information it needs. From a progressive perspective, requiring everyone to work digitally may seem the obvious answer. It establishes one source but does not explain the three missing requests.
A comparison reveals that two requests were ticked off on paper without being closed digitally. A third was verbally withdrawn and erased only from the board. The discrepancy concerns status updates. It does not establish that paper is more reliable or that the digital tool is unsuitable.
What must survive the transition?
The colleagues look at the morning round together. The board shows only work needing attention that day; the digital list includes future requests. A daily filter could preserve the useful selection without maintaining two lists. Withdrawn requests also need a visible status rather than disappearing.
| Comment | Possible concern | Joint question |
|---|---|---|
| “The board works already” | The daily selection is immediately visible | Can the new list provide that selection? |
| “Digital is the future” | Both locations need access | Which action keeps the status current? |
| “Keep both, just in case” | The handover is not yet trusted | What focused check can replace duplicate entry? |
These questions concern the work, rather than persuading a supposedly difficult colleague. A filter can function correctly and still be unreadable where the morning round takes place. That calls for checking the actual setting, not judging willingness to change.
Give duplicate work an endpoint
For the following week, those responsible designate the digital list as the authoritative source. The daily selection is viewed on an available screen during the round. On the first two days, both colleagues compare the requests discussed with their recorded status afterwards. They stop updating the paper board. If the system is unavailable, a temporary note is entered once after service returns.
This provides a fallback without creating two permanent records. If the screen proves unusable, the arrangement needs fixing before the board is removed. That specific implementation problem does not automatically invalidate the transition.
Three agreements make the decision concrete:
- Function before format. Name what the familiar action protects and show how the new process provides it.
- One authoritative source. Establish where an update counts and how temporary notes reach it.
- An explicit retirement decision. Agree who can stop the old process and which unresolved usability issue still prevents that.
Comparing personal user guides can open a discussion about the reassurance needed to let something go and the existing step that obstructs a useful change. Neither answer dictates a solution. Together they clarify what both colleagues need to assess in the same transition decision.
Comments
No comments yet. Share the first one.