Description
A case study is a narrative description of how your goals are being served by Pants. We encourage publishing either on your blog or ours. This is easily one of the most powerful things you can do to support Pants. There is no fixed format, but typically is roughly like this:
-
Introduction to the organization, its larger goals, needs, a problem it was experiencing and what they needed from a solution. What is the organization's industry niche? What is the writer's role? What challenges were you facing related to the problem? Were there constraints such as time or budget that needed to be factored it? What impact was the problem having on operations, productivity, or profitability? Etc.
-
Prospective solutions that the organization evaluated, and their pros/cons. How well did they fit the constraints? Did they live up to expectations? How easy was it to follow documentation and get support? Did the explorations cause you to revise expectations or gain new insights into the original problem? Etc.
-
Implemented solution (Pants!) and why you chose it. How did process of adoption and training go? What lessons have been gained from the process? What reflections can you share on what you'd do differently in the future or will add over time? Any tips for others who have problems similar to what you set out to solve? Etc.
-
Conclusion summarizing the takeaways.
A case study can be as short or long as you deem appropriate. The important thing is that you're just telling a story about how one individual or team dealt with their distinctive situation, sharing knowledge that can lend insights for others to benefit from.
If you'd be interested in contributing a case study about how your organization is Pants, or have already published one, let us know on Slack or here in the issue. Thank you!
Activity