One way to minimise project costs

…and obtain the solution that’s just right.

One way to minimise project costs

Highlight, Solution, Uncategorized

No business can afford to ignore the digital age, but many balk at the cost of digitization. There are ways to minimize those costs and still get what you need from your investment. Here are a few tips on how to make the most of your money while going digital.

The User Story is a document that helps you work out what needs to happen before something else happens. The difficulty with this approach, though? It requires patience and a little focus.

When done right, these stories will save your butt by making sure everything has been planned out ahead of time so there are no surprises later on down the line – even if things change drastically in those hours between now & next week

 

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 varying understandings of the “requirement”,  but people outside your business and less familiar with your operational nuances, will have 1001 interpretations.

This leads to deployment by error correction, as the system is deployed and adjusted multiple times. User Stories minimise that.

User Stories shaped by each team member’s expertise, outlines what needs solving and who will be doing it, to avoid misinterpretations.

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:

  1. R…
  2. S…
  3. 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.

With our experience in crafting UIs, we can help you agree on and develop user stories that meet your needs. We have a team of experts who will make sure the interface is designed perfectly for what it does; saving time as well as money!