Solved

Template Building

  • 8 January 2024
  • 9 replies
  • 123 views

Userlevel 2
Badge

Hi Everybody! 

When it comes to building  templates, do you find it best to write out your current practices or rather research ways to improve upon your foundation? What tools have you found to strengthen your operations? Thank you!

icon

Best answer by Victoria Peters 12 January 2024, 16:53

View original

9 replies

Userlevel 7
Badge +15

Hi @Lauren Lewis,

Great question 🙂

We definitely haven’t found the best way yet! But I think it all comes down to.. time and urgency.

Options are (probably in order of least time intensive to most):

  1. Setup templates to match existing/current processes (no change)
  2. Setup templates to match existing/current processes but tweak to improve as writing
  3. Find a best practice process and adapt it to your own dealbreaker processes

At the end of the day, I think 2 is the best middle ground.. 2 or 3 relies on a time investment (and who in the team will make that investment.. often the decision makers are the ones without enough time to make calls on the changes).

If adapting the process is urgent - decisionmakers will have to set aside the time to work on it!

Userlevel 6
Badge +7

@Lauren Lewis We do the following:

  • Create template with our current procedures,
  • Obtain feedback from users regarding how the process/template works,
  • Document process improvements within a Karbon work item task.

Once we have a starting template we are always looking for increased efficiency. I have a recurring work item setup for our practice where team members can add in feedback for our templates as they come across them. During our less busy times we review and determine what should be revised within a template.

There is no perfect, just progress. I start with where I am and go with that, revising as the need arises.

Userlevel 4
Badge +5

When we try to document a process, we started using loom to record a video BUT we also use the transcript and edit that into a list of steps - beats writing everything from scratch.

 

 

Userlevel 2
Badge

Thank you everybody! Such good feedback. I definitely agree with laying out your current procedures and then building from that. Much easier to see where you are and create better efficiency from there rather than starting from scratch. Thank you!! Also I @Ken Rogers I love the idea of using Loom as well, very interesting way of teaching people. 

Userlevel 6
Badge +7

@Ken Rogers When we do the Loom recordings, we also start Scribe. Benefit is having Scribe do the transcript with images in a step-by-step format. My two go to apps for process documentation. Some team members hate videos and prefer the Scribe.

Userlevel 2
Badge

Thank you, @LD7E, that’s an great tip!! 

Userlevel 7
Badge +10

Loved all of this!

I would also add, test, test, test - especially automators.  I have set up dodgey automation more than a couple of times! 

We have a Test Contact that the team is free to use to test work items.  When we have a winner, we will convert it to a template or update the template we were trying to tweak.

For new processes I like to work from a list in Word or Excel.  Once I have the order of tasks sorted I copy and paste to Karbon, set up sections and add automators.  I love the ‘split into tasks’ that Karbon offers.  This is so useful when templates are being suggested by team members who are intimidated by the thought of building a template in Karbon, they simply send me the process in a doc.

I also try to meet with a cross sections of team members who will be using the work item once we have a draft.  Unintended consequences, tasks that can be combined or reordered, missing steps often come up through these conversations.  There is the added benefit of buy-in when the bigger team is consulted.

And finally, I like to add a detailed description to the tasks when building a template.  This adds so much clarity to the task. As long as this is current it can save so much time as the work passes through team members, new people join or take on the work.  We have included links and Loom videos in these descriptions where appropriate.  

Userlevel 2
Badge

This is such valuable information!! Thank you so much, @Victoria Peters!! 

Userlevel 3
Badge +1

Loved all of this!

I would also add, test, test, test - especially automators.  I have set up dodgey automation more than a couple of times! 

We have a Test Contact that the team is free to use to test work items.  When we have a winner, we will convert it to a template or update the template we were trying to tweak.

For new processes I like to work from a list in Word or Excel.  Once I have the order of tasks sorted I copy and paste to Karbon, set up sections and add automators.  I love the ‘split into tasks’ that Karbon offers.  This is so useful when templates are being suggested by team members who are intimidated by the thought of building a template in Karbon, they simply send me the process in a doc.

I also try to meet with a cross sections of team members who will be using the work item once we have a draft.  Unintended consequences, tasks that can be combined or reordered, missing steps often come up through these conversations.  There is the added benefit of buy-in when the bigger team is consulted.

And finally, I like to add a detailed description to the tasks when building a template.  This adds so much clarity to the task. As long as this is current it can save so much time as the work passes through team members, new people join or take on the work.  We have included links and Loom videos in these descriptions where appropriate.  

This is a great tip @Quynh Ngo 

Reply