WCRC Analysis
A survey released by Pave, part of Quickbase, on 28 October raises a practical workplace question: who maintains a tool once the employee who built it has made it useful to everyone else?
The publisher’s findings say 24% of surveyed employees had built an app they used for work. Among app builders, only 14% said their organisation had designated someone to maintain and support their applications.
Those findings come from vendor-sponsored research. The September surveys covered 5,177 employees and 527 business leaders in the United States, sampled separately and not matched by employer. They cannot demonstrate that an employee and their own manager gave contradictory accounts of the same workplace.
The support question nevertheless deserves an answer wherever a self-built tool becomes part of a team’s work.
Useful work creates an obligation
WCRC’s Culture Crest model overview puts attention on teams and on whether an intervention worked. Applied as a management lens, that means looking beyond the person who can demonstrate an application. The team using it needs an account of the work that follows.
Consider a hypothetical tool that consolidates a recurring internal report. Colleagues begin relying on it. A change in the source data then breaks the output while its creator is on leave. The original time saving has become a service expectation, but the arrangement may still depend on one person’s availability.
WCRC would ask whether maintaining the tool is recognised in that employee’s workload. If management accepts the benefit, it should also decide what support the team can reasonably expect. Praise for initiative does not allocate time for updates or provide a substitute when the builder is absent.
This example illustrates a management risk. It is not an incident reported by the survey or a finding about Quickbase’s own employees.
Judge the whole delivery cycle
The Karma component of the Guru Codex Four-Yoga Leader Model concerns work and execution. In this setting, WCRC would apply it to the complete delivery cycle: a tool has to keep working under the conditions in which colleagues actually use it.
A reasonable handover would identify the work the application supports, the person responsible for changes and the alternative process if it fails. The appropriate review would also depend on the information involved. An internal convenience tool and an application handling sensitive data warrant different scrutiny.
The builder should be able to obtain that scrutiny without becoming responsible for decisions outside their expertise. Where security or reliability review is necessary, the employer needs to provide a route to it and recognise the time it takes.
Culture Crest’s team-level perspective also changes the proposed measure of success. WCRC would examine whether the application reduces total effort after support and correction work are included. A faster first demonstration is insufficient evidence of a sustainable improvement.
Pave’s survey describes respondents’ reported experience; it does not establish the return from any particular tool. The operational decision remains with the employer. Once a useful application becomes a shared dependency, the maintenance arrangement should become shared knowledge too.