Tuesday, August 25, 2020

2020 #VWEDU: #DTA: Computational thinking in preparing instructions: Design thinking: Use-case analysis: Micro-learning JIT learning

Computational thinking in preparing instructions: 
Design thinking: Use-case analysis: 
Micro-learning: JIT learning

How to design instruction pages to fit use cases that users want.

Computational thinking in preparing instructions

  • Design thinking: What do the users need?
  • Users always have a specific use in mind: that is a use case.
  • Instructions are part of the product.  A user wants instructions for a use case.
  • Users need instructions for each use case they have.
  • At any given time, users only need instructions for the use case at hand. 
  • Each use case should have its own set of instructions.  
  • That allows microlearning for each use-case.
  • And supports JIT learning.
  • Microlearning needs microcredentials (badges).
  • Not just to provide evidence of competence
  • But also to tell learners what they need to do be competent.

Key terms, search on page

  • Design thinking
  • Use case
  • Demand
  • Market potential
  • User interface
  • JIT
  • Microlearning
  • Badge
  • Search on page: Ctrl+f opens search bar near the top of the page.
  • Search on page is an element of JIT learning.

Algorithm for preparing instructions

  • An algorithm, for people not computers. 
  • I said computational thinking.
  • Collect and obvious use cases.
  • Do the use cases have enough collective demand to support the product?
  • If no, branch to something else. 
  • For each use case estimate the potential market.
  • Order the use cases in descending order by market potential.
  • For each use case:  Iterate over use cases.
  •   Write detailed specifications of what the user must do to complete the use.
  •   If the number of steps exceed 5 (TBD):
  •     Review the user interface to simplify it.
  •     Do not use instructions to cover the failings of the user interface.
  •    Go to subroutine Debug use case instruction.  
  • END For each use case.

Debug use case instruction

  • Get sample of users who would use this use case.
  • Prepare instances of use case
  • Tell users these are intended to be JIT instructions for this use case.
  • Each user is to read the instructions and execute a use case.
  • Each user is instructed to ask questions as needed.
  • Any question indicates a bug in the instructions.
  • Computational thinking is not about ignoring bugs.


Example of design thinking in digital worlds

Examples of use-case analysis in digital worlds

Examples of  microlearning and JIT instructions in digital worlds


Visit me on the web

  • Drop by my web offices Weekdays: 12:-12:30 pm Central time (US)
  • I am available for free consulting on any topic in this blog.
  • Cybalounge and 3DWebWorldz (Orientation room)
  • I will be in both places, so you may need to speak to get my attention.
  • Web-worlds, 3D virtual worlds running in a browser. Summary
  • And we can visit the Writer's Workshop on the Web
  • Don't register -- enter as guest.  


  • Original text in this blog is CC By: unless specified public domain.
  • Use as you please with attribution: link to the original.
  • All images without attribution in this blog are CC0: public domain.
  • Screenshots from ShareX
  • Second LifeLindenSLurl, and SL are trademarks of Linden Research Inc.
  • Annotated screenshots made with Techsmith Capture
  • This blog is not affiliated with anything.   Ads are from Google.
  • Selby Evans in Kitely and Hypergrid, Thinkerer Melville in Second Life.

No comments:

Post a Comment