Distinguish ideas, innovation and problems

A scheduling center says it has an “innovation” because a team drew a new booking screen. Before repeating that label in a report, ask what actually changed for service users and whether anyone could use the screen. The distinction matters to a specialist: funding a test, announcing an outcome, and measuring an effect are different decisions at different stages. An idea proposes a possible change. A prototype represents a possible change so that a team can learn before operation. In the Oslo Manual's measurement framework, an innovation is a new or improved product or process that differs significantly from the unit's previous offering or process and has been made available to users or brought into use. This is a working classification for the case, not a certification awarded to the organization.

Start with a baseline. Record how the task is performed today, rather than how a manager assumes it is performed. In this fictional center, a customer books by phone and calls again after a change; an employee enters the change manually. Giving an internal page a new color, while nobody uses it, tells us neither whether the customer benefited nor whether the service changed. A text message confirming a change, if actually sent to customers, is an observable change. It may be new to this center even if other centers already use it. State the unit of comparison: “new to this center compared with its previous booking path” is supportable here; “first in the market” needs separate evidence.

Do not begin with a proposed solution. A problem describes a gap between the outcome someone needs and what occurs. “We need an app” assumes a solution. “In one week's sample, 28 of every 100 customers called again to confirm a changed appointment” is a testable observation, provided the denominator and source are defined. A review might show that customers call because confirmation arrives late, because they doubt its accuracy, or because the change itself is missing. Each explanation calls for a different test. One number does not establish a cause; the specialist lists competing explanations and seeks evidence that separates them.

Use a four-line classification card: (1) baseline and comparison unit; (2) the specific change and its users; (3) evidence that the change was made available or used; and (4) evidence of benefit or harm, with uncertainty. Line three separates an implemented outcome from innovation activity still in progress. Line four prevents another common error: implementation does not prove success. A new service may be available yet save no time, or help one group while burdening another. Agree on a defined denominator, period and data source before claiming an effect.

If sending or use logs are missing, a slide deck is not evidence of implementation. Request a dated, scoped sample of operational evidence, within authorized data access. If employees' accounts conflict with a system record, log the discrepancy and identify a checkable event instead of picking the more flattering story. The specialist can prepare a truthful initiative description and propose the next test within an assigned mandate. Organization-wide launch approval, customer-data processing decisions, and legal or intellectual-property conclusions belong to the authorized owners.

Implementation and diffusion differ. A library may use a new procedure in one branch, making bounded implementation a fair description, while “the whole organization uses it” is false. Always state where, when and who could use the change. Fewer calls in one branch also cannot be projected onto every branch without considering visitor and staff differences. If an operating process stops after a day because of failure, report the actual use period rather than presenting it as lasting success or denying it was ever used. The four-line card helps: branch baseline, change offered, actual use record and outcome still unverified. Keep “new to this unit” separate from “new to the world.” The former may support analytical classification when significant difference and use are shown; the latter needs wider external research.