<Thing worth managing> is… Put a brief definition here, a sentence up to a paragraph. If you have a picture that captures the TWM, add it as the featured image for the listing. Use royalty-free pics from pixabay or pexels; maximum file size for upload is 128 MB.> Desired States
Performance is effective when…
State what good looks like, what we are achieving by driving towards achieving and maintaining a desired state for a thing worth managing. So put a paragraph or aim for 5-7 bullets that answer the question “Perdormance is effective when…” This should be a statement of the standard for what good looks like. Consider talking in the first person, starting bullets or sentences with “we”. Best Practices
Why is <TWM> a thing worth managing?
State here in a paragraph why this must be managed, what happens well when it is managed that is positive, what happens negative when it is not. How to do it
Make a list of all the specific things worth managing, under the categories Stakeholders (customers, users, provider, suppliers)
For each, identify the 3 types of events you want to be informed of, with alerts: informational, warning, exception. Rate the events by priority.
Put in place mechanisms that trap these events and generate alerts, automating mechanisms in priority order..
Monitor and control events. Establish a rhythmic pattern of reporting and review and action.
Practice continuous improvement, based on what your telemegey / instrumentation is telling you.
Aim for establishing monitoring and control in priority order, with a system you can manage, so not all possible monitors and controls but the most important ones currently, just as you would do for your health. we
IRL (Real world example)
In real life, you might be concerned with maintaining a state of health for a process, like change handling, or an IT-led service, like your order entry system, a human-led service, like moves, adds and changes, to a function like your team, to tooling, like your ticketing system, to individual moments of truth like your post mortems, or your employee, customer, user and supplier satisfaction.
For example, Walt owns the health of his chat box system that appears on the elearning website for sales inquiries, support and so on. For event handling, he is most concerned when users have technical difficulties with the site. His priorities are to know of and fix any issues quickly, first for issues that affect all users, then individual courses, and lastly individual users. So walt builds that prioritization scheme into the cat ticketing system scheme. Next, Walt wants to put some thresholds in place to make sure certain things stay under control. For example, the elearning hoster charges additional fees for each active user over 500, so he puts a notification in place when 450 active users is reached so he can go in and clear out users who haven’t logged in for over a year and mark them inactive to free up headroom. Lastly, Walt wants to be informed about key statistics like concurrent users, usage by hour by day, by region, most popular topics, quiz pass rates and so on, so he stands up these analytics in the LMS.
Where to go
To learn more about this thing worth managing General Information
Stick links and short descriptions of what’s there (no more than a sentence), to the best general information on the topic out there. Generic Job Aids for this thing worth managing
Stick links and short descriptions to the best job aids (downloadable worksheets, posters, online calculators, free tools, etc.) for the thing worth managing. Vendor, Tool and Platform-specific Guidance & Job Aids for this thing worth managing.
Stick links and short descriptions for the best vendor, tool and platform-specific guidance out there for this thing worth managing.