Start a conversation

What is the difference between a "Teylu Topic" and a typical "Small Group Study Guide"?

If you’ve been in a small group, there’s a good chance you have used a study guide. There are two primary differences between a study guide and a Topic.

Conversation, not consumption led

Study guides are aligned with the status quo teaching model that assumes the teacher’s job is to impart knowledge and the students are simply there to consume everything sent their way.

Teylu Topics are not this.

Whilst there is room for some consumption of material suggested by the creator, a Teylu Topic expects more from Members than consumption. It expects them to contextualise the material and own any way forward.

User ownership, not teacher liability

Study guides are aligned with the status quo teaching model that assumes the quality of the "course" is almost entirely dependent upon the quality of the teacher. As such, the responsibility - and any potential blame - lies primarily with the educator.

Teylu Topics are not this.

Whilst it should never be used as an excuse to provide poor material, the Teylu Members carry an equally high degree of responsibility for whether the content works well. The quality of the discussion is far less dependent upon the material than it is their willingness to be open, vulnerable and courageous. The best material in the world is no substitute for high quality, transparent dialogue.

Add to the expert, not match it

Study guides are aligned with the status quo teaching model that assumes all that could be known on the topic already does and that students cannot, or are unlikely to, add to the greater body of knowledge on the issue.

Teylu Topics are not this.

Whilst they assume some knowledge on the part of the creator, they equally assume that Teylu Members can add to that knowledge, not simply rise to match it. For example, they can bring some fresh perspective, experience or insight into the issue.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. John Featherby

  2. Posted
  3. Updated

Comments