Skip to content

Commit e93665f

Browse files
authored
Merge pull request #95 from Relequestual/docs/case-study-template
Add case study template for feedback and comments
2 parents 70d3265 + 0302975 commit e93665f

File tree

1 file changed

+43
-0
lines changed

1 file changed

+43
-0
lines changed

docs/case-studies/template.md

+43
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# Case Study Template
2+
3+
## Preface
4+
5+
In looking to publish at least three case studies this year, we need a template of questions to ask organizations.
6+
Here are a list of questions which we should provide for each case study.
7+
The questions themselves should not be in the case study, but we should be able to put the resulting answers together should provide us with a mostly workable case study.
8+
9+
The list is mostly based on the case study format used at https://www.cncf.io/case-studies.
10+
11+
For each question or group of questions, before the dash is providing context, and would not be sent to the case study subject.
12+
13+
We should always seek final approval for the case study subject before publishing.
14+
15+
## Questions
16+
17+
Challenge - What challenges were you encountering before you used JSON Schema?
18+
19+
Solution - In what way did JSON Schema solve this challenge?
20+
21+
Impact - What was the impact of the solution? What benefits have you seen?
22+
23+
Key impact results - Are there any metrics you used to evaluate the impact or success of the project using JSON Schema?
24+
25+
---
26+
27+
Who is your organization, and where do you or your group/team sit within it?
28+
29+
What is the organization's mission? What is your group's/team's mission?
30+
31+
What’s the organization's story that led to this work?
32+
33+
How the challenge arose - What was the situation before the challenge presented? Was there a solution which didn’t meet new requirements?
34+
35+
Considerations during research for a solution - What criteria did you use when deciding on potential solutions? What potential solutions did you decide were not as good a fit and why?
36+
37+
"A Ha!" moment - What was the moment or key feature of JSON Schema that meant it was the right solution for you to try?
38+
39+
Wider influence? - Has your/your project's use of JSON Schema had influence in other areas of the organization?
40+
41+
What assurances do you now have? - Does JSON Schema provide you with any confidence looking forward to the future?
42+
43+
Additional meta-data if possible: Industry, location, Size... ?

0 commit comments

Comments
 (0)