Advice on demonstrating complex troubleshooting steps

Please unsubscribe me from these emails. I was not able to unsubscribe by clicking on your link at the bottom of the page.

Thanks.

SAU C LOW
Learning Designer
TAFE DIGITAL
T +61 2 9715 8924 | M +61 0469 409 436
E sau-chee.low@tafensw.edu.au

TAFE NSW
51 Wentworth Road Strathfield, NSW 2135
tafedigital.edu.au

[cid:image001.png@01D35A38.6911F7D0]
[Title: FaceBook link icon - Description: TAFE NSW FaceBook link icon][Title: LinkedIn link icon - Description: TAFE NSW LinkedIn link icon][Title: YouTube link icon - Description: TAFE NSW YouTube link icon][Title: Twitter link icon - Description: TAFE NSW Twitter link icon][Title: Instagram link icon - Description: TAFE NSW Instagram link icon]

We respectfully acknowledge the traditional custodians of the Country on which we learn and work together, and commit to building relationships, respect and opportunities with Aboriginal Peoples.

Hi Scott,

As I am sure you are already aware, one of the tools that is used in troubleshooting is the fault-finding chart, which is often a flow chart full of decision points based on symptoms that are encountered during fault diagnosis. At the link below I have put together a very simplistic fault finding chart using Button Stack blocks in Rise as the decision points.

This could obviously be as long and complex as you wish and, because of the nature of Button Stack blocks, it doesn't have to be restricted to just two options at each decision point.

I hope this helps to provide some inspiration.

https://rise.articulate.com/share/QXj69CEWMFKYqnUP4lsPkCbglrKU4LZc

Hi Sau, 

Looks like Wendy responded to you over here. 

Also, just thought I'd point out that when you respond directly from your email, your signature is appended to the message. You may want to pop in there and edit out any personal information that you don't want to share with the community.