Marquis Instructions

<!
DOCTYPE html>
<head>
<link
href="https://marquisdugger.com/
scorm_tut/shield_d
%2Bfavicon.png" name="favicon"
rel="shortcut icon"
type="image/png">
<link rel="stylesheet"
side_b_kb/style.css"
type="text/css">
<meta property="og:image"
content="https://marquisdugger.co
m/mfw/morton_girl_enhanced.jpeg
">
<title>Build Order</title>
</head>
<body>
<div id="nav">
<ul>
<li><a
side_b_kb/where.html"
target="_blank">BACK TO MAIN
PAGE</a></li>
</ul>
</div>
<div id="box">
<h1>DOING THINGS DECENTLY
AND IN ORDER</h1>
<h2>Contents.</h2>
<ol>
<li><a href="#before">BEFORE
READING</a></li>
<li>SO WHY ARE YOU WRITING
THIS ARTICLE?</li>
<li><a href="#start">GETTING
STARTED.</a></li>
<li>OKAY, SO NOW WHAT?</li>
<li>WHAT CLIENTS WILL
COMPLAIN ABOUT OR
MISUNDERSTAND.</li>
<li><a href="#track">SCORM
AND TRACKING THINGS</a></li>
<li><a
href="#end">CONCLUSION</a></
li>
</ol>
<h2>Before Reading</h2>
<p>Even in the simplest of
interfaces, determining what is
best to do at any given time is
hard without plenty of prompting
and guidance. This guide is meant
to help provide suggestions you
can share with clients as best
practices for getting the platform
setup in general and give that AAA
customer service we want to be
famous for.</p>
<h2>So where do we start?</h2>
<p>Regardless of use-case, all
clients have a similar set of goals
to accomplish. What are are
aiming for here is to tackle the
most common problems clients
have run into and address those.
To guide our thinking, let's use
questions as a basis for making our
list. Those questions would
be:</p>
<ul>
<li>How am I organizing my
users?</li>
<li>What do I want them to learn?
</li>
<li>What happens if they learn it?
</li>
<li>How are they getting access to
what I want them to learn?</li>
<li>How do I make sure users are
informed about what's happening?
</li>
<li>How do I make sure to
measure what's happening in my
platform so I can make
adjustments?</li>
<li>What do I do if I need help or
knowledge?</li>
<li>How do I get people into this
world of my own making?</li>
</ul>
<p>There it is. The answers vary
in their depth and complexity, but
these are the core things. You'll
find that answering these
questions with a few moments of
<emphasis>but why</emphasis>
should get you where you want to
go.</p>
<h2>That's spiffy, but how about
something more concrete?</h2>
<p>Generally speaking, here's
how you want to build things.</p>
<ol>
<li>Build branches and
groups.</li>
<li>Add custom fields.</li>
<li>Build courses.</li>
<li>Create catalogs and learning
plans.</li>
<li>Build certificates and
recertification paths.</li>
<li>Create notifications and/or
reports and/or dashboards.</li>
<li>Create reports and/or
notifications and/or
dashboards.</li>
<li>Create notifications and/or
reports and/or dashboards.</li>
<li>Add users and shake
well.</li>
</ol>
<p>The above assumes that
automation isn't happening. This
includes:</p>
<ul>
<li>Automation rules</li>
<li>Enrollment rules</li>
<li>API Integrations</li>
<li>SAML/ADFS</li>
<li>LDAP</li>
</ul>
<p>These are subject to
conversations that usually start in
implementation, but you'd insert
the automated processes into the
places they occur in the flow.</p>
<blockquote>I'mma need you to
justify this order</blockquote>
<p>Fair enough. Here's the
idea:</p>
<ul>
<li>You need groupings to
determine what access goes to
whom later in terms of course
assignment/access and user
management for power users. You
want to do this first or you don't
have things to attach power users,
learning plans, catalogs to.
<ul><li>Addendum: if you have
power users, <strong>add them at
this stage</strong>. You can
thank me later.</li></ul></li>
<li>You add custom fields in case
you need them for sorting (if you
have groups) or reporting.</li>
<li>You need courses because
making catalogs or learning plans
without the pieces to place into
them is just time wasted when you
have to come back to the same
place later. <emphasis>Non
essere stupido
grazie</emphasis>.</li>
<li>I think building catalogs and
learning plans at this point is self-
explanatory.</li>
<li>You need certificates here
because having them applied
retroactively is an absolute
nightmare and requires
professional services. Just
don't.</li>
<li>Notifications, reports, and
dashboards are not related and
therefore interchangeable. Do
what you want, but do all three of
these things.</li>
<li>If you've set everything else
up, then this is the fun part.</li>
</ul>
<h2>Conclusion</h2>
<p>Take these suggestions and
make some people successful.
They will thank you for your
wisdom, you will be relieved
because it worked and unicorns
will start grazing in your front yard.
I've seen it happen.</p>
</div>
<footer>
<ul>
<li><a
side_b_kb/where.html"
target="_blank">BACK TO MAIN
PAGE</a></li>
<li style="text-transform:small-
caps;">LAST UPDATED: 10 JAN
2017</li>
</ul>
</footer>
</body>

Marquis Instructions

Uploaded by

Copyright:

Available Formats

Marquis Instructions

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Marquis Instructions

Uploaded by

Copyright:

Available Formats

<!

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.