Skip to content

Commit cc3ffec

Browse files
authored
Update case-study-guidelines.md
Signed-off-by: Katie Greenley <[email protected]>
1 parent 74a1cba commit cc3ffec

File tree

1 file changed

+43
-54
lines changed

1 file changed

+43
-54
lines changed

case-study-guidelines.md

+43-54
Original file line numberDiff line numberDiff line change
@@ -13,40 +13,38 @@ The CNCF End User Stories Program features real-world use cases and the impact C
1313
* Open to all Platinum and Gold End User Members
1414
* Leveraging CNCF’s [Online Programs](https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md) to showcase a case study webinar or submit a pre-recorded video case study for our YouTube channels
1515
* Open to all CNCF members
16-
* Participate in the [End User Lounge livestream](https://www.cncf.io/blog/2021/04/22/introducing-the-cncf-end-user-lounge-exclusive-live-streams-for-end-user-organizations/) - a program that offers exclusive live streams for end users to showcase how they navigate the cloud native ecosystem
17-
* Open to all End User Members
1816

1917

2018
## Written Case Study ##
2119

2220
### Who can be featured in a case study? ###
2321

24-
Case studies feature organizations working with CNCF incubating or graduated projects. If you are a CNCF member (companies that build and sell cloud native solutions to external organizations) and have customers with interesting use cases, you can suggest them for a case study. The resulting case study would be about your customer’s use case, and we would also be able to include some details about how you helped with the implementation.
22+
Case studies feature organizations working with CNCF incubating or graduated projects. If you are a CNCF member (companies that build and sell cloud native solutions to external organizations) and have customers with interesting use cases, you can suggest them for a case study. The resulting case study would be about your customer’s use case, and we would also be able to include some details about how you helped with the implementation.
2523

2624
As a rule, case studies feature:
2725
* CNCF End Users (Companies that use cloud native technologies internally, but do not sell any cloud native services externally)
2826
* Organizations working with CNCF incubating or graduated projects
2927

30-
All case studies must demonstrate at least one tangible business impact of CNCF incubating or graduated projects.
31-
Examples from published case studies include:
32-
* 60% of maintenance time saved for private image central repository - [JD.com and Harbor](https://www.cncf.io/case-studies/jdcom-harbor)
33-
* Able to release 10x a day, instead of every quarter - [Vodafone and Kubernetes](https://www.cncf.io/case-studies/vodafone/)
34-
* With 4,000 pods, 200 nodes, and 80,000 builds per month, adidas is now running 40% of its most critical, impactful systems on its cloud native platform. - [Adidas, Kubernetes and Prometheus](https://www.cncf.io/case-studies/adidas/)
28+
All case studies must demonstrate at least one tangible business impact of CNCF incubating or graduated projects.
29+
Examples from recently published case studies include:
30+
* 698,000 issues discovered since start of project - [Grafana Security](https://www.cncf.io/case-studies/grafana/)
31+
* 4 million customer transactions/day - [Post Finance](https://www.cncf.io/case-studies/postfinance/)
32+
* 200% through-put improvement - [SysEleven](https://www.cncf.io/case-studies/syseleven/)
3533

3634

37-
### Written Case Study Process ###
35+
### Written Case Study Submission Process ###
3836

3937
To empower our fast-growing end user community to tell their stories, case studies follow a self-service partnership model - leveraging internal knowledge and expediting the sign-off process, with editorial support and guidance provided by the CNCF.
40-
38+
4139
The self-service partnership follows a five-step process:
4240

4341
**1. Proposal**
4442
* End users submit a [case study proposal](https://forms.gle/3rexeb56aDuYNMga8)
4543

4644
**2. Review**
47-
* casestudies@cncf.io team reviews proposal within 20 working days
45+
* [marketing@cncf.io]([email protected]) team reviews proposal within 20 working days
4846
* If the proposal meets the criteria, the end user is sent a [case study pack](https://drive.google.com/file/d/1a19vzDM7EZtAvBbJnkTeSVbvDp4z5Kex/view?usp=sharing)
49-
* If the proposal doesn’t meet the criteria, the casestudies@cncf.io team will provide feedback and the end user is invited to resubmit
47+
* If the proposal doesn’t meet the criteria, the [marketing@cncf.io]([email protected]) team will provide feedback and the end user is invited to resubmit
5048

5149
**3. Creation**
5250
* End user writes case study
@@ -60,73 +58,64 @@ The self-service partnership follows a five-step process:
6058

6159
**5. Publishing**
6260
* CNCF prepares the case study for publication
63-
* End user will receive a preview link, to view the case study before it goes live. This is an opportunity for final tweaks, but not to add further information.
61+
* Generally case studies are published within 30 days but the timeframe can vary. The case study team will communicate potential publication dates and/or changes to those dates
6462
* Case study is published to <https://cncf.io/case-studies>
6563
* Promotion cycle begins
6664

67-
68-
### Sample Case Study: Spotify ###
69-
An Early Adopter of Containers, [Spotify Is Migrating from Homegrown Orchestration to Kubernetes](https://www.cncf.io/case-study/spotify/)
70-
71-
An early adopter of microservices and Docker, Spotify had containerized microservices running across its fleet of VMs with a homegrown container orchestration system.
72-
73-
Kubernetes was a nice compliment to their homegrown system, so the migration to Kubernetes and other CNCF projects went smoothly. Spotify is using Kubernetes, Envoy, and gRPC.
74-
75-
Results:
76-
* CPU utilization improved 2-3x
77-
* Services creation went from an hour to seconds or minutes
78-
* Spotify has thousands of microservices in production, 150+ running on Kubernetes.
79-
80-
8165
### Promotion ###
8266
Case studies are published on [cncf.io](https://www.cncf.io/newsroom/case-studies/), feature in rotating hero images on the cncf.io homepage, and, in some cases, features on specific project websites.
8367

84-
CNCF markets the case studies online, through social media, blog promotion, and the CNCF newsletter. In some cases, the case study will be shared via the project Twitter account. End users are encouraged to leverage CNCF’s numerous marketing channels to amplify their case study. We ask that you share the case study on your platforms as well.
85-
86-
87-
### To get started ###
88-
89-
Propose a case study and send it to the team directly with [this form](https://forms.gle/3rexeb56aDuYNMga8)
68+
CNCF markets the case studies online, through social media, blog promotion, and the CNCF newsletter. In some cases, the case study will be shared via social media. End users are encouraged to leverage CNCF’s numerous marketing channels to amplify their case study. We ask that you share the case study on your platforms as well
9069

9170
### Summary ###
9271

93-
If you have any questions or feedback about the Written Case Study program, please email [email protected].
94-
72+
If you have any questions or feedback about the Written Case Study program, please email [[email protected]]([email protected]).
9573

9674

9775
# End User Journey Report #
9876

9977
### Who can be featured in an end user journey report? ###
10078

101-
End User Journey Reports are comprehensive deep-dives, demonstrating how organizations have grown as cloud native technology leaders. EUJRs are open to CNCF Platinum and Gold End User Members who have developed mature cloud native systems. Participants are leaders in their field and want to use their position to inspire and educate others.
79+
End User Journey Reports are comprehensive deep-dives, demonstrating how organizations have grown as cloud native technology leaders. EUJRs are open to CNCF Platinum and Gold End User Members who have developed mature cloud native systems. Participants are leaders in their field and want to use their position to inspire and educate others.
10280

103-
### End User Journey Report Process ###
81+
### End User Journey Report Submission Process ###
10482

105-
EUJRs are managed, written and produced by CNCF, in close collaboration with End User Members.
83+
End User Journey Reports are managed, written and produced by CNCF, in close collaboration with End User Members.
10684
Participants will need to:
107-
* Complete initial proposal which covers:
108-
* How long have you been using CNCF projects?
109-
* Which projects do you use?
110-
* Has your organization contributed to a project/donated a project?
111-
* Do employees of your organization take an active role in CNCF -- for example, chairing committees, or speaking at KubeCon-CloudNativeCon?
85+
**1. Proposal**
86+
* To participate in an End User Journey Report, submit a [proposal](https://forms.gle/y2wqydF1hVGBRXGEA)
87+
* Complete initial proposal which covers:
88+
* How long have you been using CNCF projects?
89+
* Which projects do you use?
90+
* Has your organization contributed to a project/donated a project?
91+
* Do employees of your organization take an active role in CNCF -- for example, chairing committees, or speaking at KubeCon + CloudNativeCon?
92+
93+
**2. Review**
94+
* [[email protected]]([email protected]) team reviews proposal within 20 working days
95+
* If the proposal meets the criteria, the marketing team reaches out to set up an interview
96+
* If the proposal doesn’t meet the criteria, the [[email protected]]([email protected]) team will provide feedback and the end user is invited to resubmit
97+
98+
**3. Creation**
11299
* Nominate 1-2 employees to take part in an hour-long interview
113-
* Possibly take part in a follow-up interviews to fact-check and clarify information
100+
* CNCF writes end user journey report
101+
102+
**4. Editing**
103+
* Take part in a follow-up interviews to fact-check and clarify information
114104
* Approve written content
115-
* Approve final designed content
105+
* Approve final designed content
116106

117-
### Sample End User Journey Report: Spotify ###
107+
**5. Publishing**
108+
* CNCF prepares the end user journey report for publication
109+
* Generally end user journey reports are published within 30 days but the timeframe can vary. The case study team will communicate potential publication dates and/or changes to those dates
110+
* Case study is published to <[https://cncf.io/reports](https://www.cncf.io/reports?_sft_lf-report-type=end-user-journey)>
111+
* Promotion cycle begins
118112

119-
**Coming soon!**
113+
**Sample End User Journey Report:[Adobe](https://www.cncf.io/reports/adobe-end-user-journey-report/)**
120114

121115
### Promotion ###
122116

123-
End User Journey Reports are published on cncf.io and marketed through social media, blog promotion, and the CNCF newsletter. Participating End Users may be asked to join media interviews or speaking opportunities with CNCF leaders.
124-
End users are encouraged to leverage CNCF’s numerous marketing channels to amplify their End User Journey Report. We ask that you share the report on your platforms as well.
125-
126-
### To get started ###
127-
128-
To participate in an End User Journey Report, submit a [proposal](https://forms.gle/y2wqydF1hVGBRXGEA)
117+
End User Journey Reports are published on [cncf.io](cncf.io) and marketed through social media, blog promotion, and the CNCF newsletter. Participating End Users may be asked to join media interviews or speaking opportunities with CNCF leaders. End users are encouraged to leverage CNCF’s numerous marketing channels to amplify their End User Journey Report. We ask that you share the report on your platforms as well.
129118

130119
### Summary ###
131120

132-
If you have any questions or feedback about the End User Journey Report program, please email casestudies@cncf.io.
121+
If you have any questions or feedback about the End User Journey Report program, please email [marketing@cncf.io]([email protected]).

0 commit comments

Comments
 (0)