# Content design tips Our documentation focuses on the technical aspects of Instruqt such creating tracks, challenges, scripts, and track invites. With that being said, there is an important step you should consider before building a track: **design**. No matter how excellent your software is, your learners will drop out if your track is not designed effectively. This guide provides high-level insight on how to design effective and engaging tracks so your learners leave your tracks happy and educated. ## The three learner types you should consider The foundation of effective track design is to consider the different learner types. Because when it comes to learning, you can distinguish three types of learners: * The Listeners, who learn by hearing something explained to them. * The Watchers, who learn by watching something demonstrated to them. * The Doers, who learn by doing something according to instructions given to them. Just picture one of your former school classes, and you will recognize these three types. It is crucial for you to serve all the learner types to make your tracks successful. ## How to captivate each learner type Recognizing the different learner types is half the equation. You will also need a method to captivate the different learner types in your tracks. To captivate each learner type, you should apply the TSD method in your tracks. TSD stands for: * Tell * Show * Do *Tell* means you explain your software by telling your learners how it's organized or works. The telling can also be (partly) in writing. *Show* means you explain your software by demonstrating it. The showing can also cover diagrams or other visuals. *Do* means you give your learners your software plus instructions and assignments and let them try and discover. And together, they form TSD, which satisfies all learner types because: * The Tell-part serves the Listeners. * The Show-part serves the Watchers. * The Do-part serves the Doers. {% hint style="info" %} **Bonus when applying TSD** Applying TSD in your tracks ensures you satisfy all your learner types, but you and your learners will also get a bonus, as this saying goes: > Tell me and I will forget;\ > Show me and I will remember;\ > Do and I will understand. > {% endhint %} Now let's see how you can bring TSD into your tracks. The focus is on challenges and these three challenge parts: * Assignment text * Notes * Tabs And the following describes how you can use these parts regarding TSD. ### Tell and show with the assignment text Each challenge is introduced and accompanied by an assignment text like the following:

Example assignment text

### Tell and show with Notes Each challenge can be preceded with notes that introduce a challenge or give extra information to the learner:

Example note page

You can base notes on texts, images, or video files. And again, this serves the Listeners and the Watchers. Especially video files can be very effective as they appeal to both the Listeners and the Watchers. ### Do with Tabs Each challenge can have one are more tabs that expose terminals or editors where learners can enter commands or create code:

Example terminal tab

Example VS Code tab

You can add tabs with accompanying tasks (in the assignment text) to fulfill, which serves the Doers among your learners. To further support the Doers, you can add [challenge check scripts](/sandboxes/lifecycle-scripts/add-a-script-to-check-challenge-execution.md) to help them when they get stuck or reward them when they succeed. ## Apply TSD to design effective tracks Design is a creative process by nature. You can propose a design flow and method like in this document, but you cannot give a detailed sequence of 'do this, do that'-instructions for designing. So it's up to you and your creativity to apply TSD in your track design. And when you do so, you will discover that the TSD balance differs from track to track. A track with the goal to inform about your software will focus on telling and showing. And a track that aims to instruct your software will focus on doing. So, yes, it depends to what extent you apply each part of TSD in a track. But always hold the three learner types in mind when you start thinking about the setup of your tracks. Make sure that you address the tell, show, and do part to engage all of your learners. Check the Instruqt [Inspiration Library](https://play.instruqt.com/inspiration-library) for examples and more ideas. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.instruqt.com/resources/design-effective-tracks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.