KWL Chart Template
Focus on important ideas and expand your learning.
About the KWL Chart template
What is a KWL Chart?
A KWL Chart is a learning tool that helps guide people through an educational session or reading. All KWL Charts contain three columns: Know, Want to Know, and Learned. You begin your session by taking stock of what you know. Then, record what you want to get out of your session. Last, you record what you have learned.
How to create a KWL Chart
Step 1 - Draw three columns. Label the leftmost column Know. In the middle, label your column Want to Know. Label the right hand column Learned.
Step 2 - Begin by listing everything you know about a topic and recording that information in the Know column.
Step 3 - Then, generate a list of questions about what you Want to Know and record those questions in the Want to Know column.
Step 4 - After your session or reading, answer your questions in the Learned column.
The Sailboat Retrospective is a low-pressure way for teams to reflect on how they handled a project. By defining your risks (the rocks), delaying issues (anchors), helping teams (wind), and the goal (land), you’ll be able to work out what you’re doing well and what you need to improve on for the next sprint. Approaching team dynamics with a sailboat metaphor helps everyone describe where they want to go together by figuring out what slows them down and what helps them reach their future goals.
So you just completed a sprint. Teams busted their humps and emotions ran high. Now take a clear-eyed look back and grade the sprint honestly—what worked, what didn’t, and what can be improved. This approach (4Ls stand for liked, learned, lacked, and longed for) is an invaluable way to remove the emotion and look at the process critically. That’s how you can build trust, improve morale, and increase engagement—as well as make adjustments to be more productive and successful in the future.
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.
Want to keep your company secure and performing soundly? You have to first know how you’ll be affected by outside elements and factors — especially those that are political, economic, social, technological, legal and environmental in nature. A PESTLE Analysis helps you identify them and prepare for them. With this easy-to-use template, you can conduct a PESTLE Analysis, then use the results to shape your strategic planning, budget allocation, marketing, product updates, and organizational change initiatives.
Brainstorming is such a big part of ideation. But not everyone does their best work out loud and on the spot, yelling out thoughts and building on others’ ideas. Brainwriting is a brilliant solution for them—creative thinkers who happen to be more introverted. This approach and template invites participants to reflect quietly and write out their ideas, and then pass them to someone else who will read the idea and add to it. So you’ll get creative ideas from everyone—not just the loudest few.
A screen flow (or wireflow) brings together a multi-screen layout that combines wireframes with flowcharts. The result is an end-to-end flow that maps out what users see on each screen and how it impacts their decision-making process through your product or service. By thinking visually about what your customers are looking at, you can communicate with internal teams, stakeholders, and clients about the decisions you’ve made. You can also use a screen flow to find new opportunities to make the user experience frictionless and free of frustration from start to end.