Ateesa adoption methodology

How to get what you want, at the lowest cost.

Ateesa adoption methodology

Adoption, Highlight

One of the most useful tools for reliable deployment of information technology is “User Stores” or “Use Cases”.

It is really painful because you need to work out what you want, in advance instead of learning by expensive trial and error, but it is worth the boredom of sitting down and documenting:

As a support worker…
I want to be able to view previous 7 days of shift hand over notes for clients I engage with…
so that when I start a shift I am forearmed and have context about issues, which allows me to better manage client outcomes for my shift.

 

As a scheduler…
I want to be able to see and be warned in advance, when clients are approaching their funding limits, at least 60 days before funding runs out …
so that I can create a report at the click of a button to engage with Plan Managers, clients, and funding sources, to set expectations and request funding review before it runs out.

 

It is surprising how few organisations do this, and since you can use your own people, which will minimise costs.

Using out-of-the-box software is a great starting point, then add the critical user stories for your business for tweaking and making sure configuration meets your needs.

Many organisations create a “Requirements” document which is easier because it is throwing ideas onto a whiteboard and seeing which ones remain, but there are 1001 ways to interpret each “requirement” leading to additional expense. Internally your team might have 501 different understanding of the “requirement” but people outside your business and less familiar with your operational nuances, will have 1001 interpretations.

Someone will be paying for deployment by error correction, as the system is deployed and adjusted 7 times.

When you have chosen the technology platform you wish to use, these User Stories can be augmented with specifics:

As

a support worker…

I want

to be able to view previous 7 days of shift hand over notes for clients I engage with…

so that

when I start a shift I am forearmed and have context about issues, which allows me to better manage client outcomes for my shift.

  1. Open x record
  2. Click y button
  3. Close and save

 

 

As

a scheduler…

I want

to be able to see and be warned in advance, when clients are approaching their funding limits, at least 60 days before funding runs out …

so that

I can create a report at the click of a button to engage with Plan Managers, clients, and funding sources, to set expectations and request funding review before it runs out.

  1. Open x record
  2. Enter data into fields
    • M…
    • N…
    • O…
    • P …
  3. Click the widget at marked “ding” at the top of the screen

The system will automatically do:

    • R…
    • S…
    • T…

Using standard products as a benchmark, then using the combined experience of your operational team to agree and develop User Stories, will save you time and money, while ensuring you get what you need.

Many organisations including ours can assist your team develop these, but your team needs to own them.