We should develop compelling internal & external use cases.

[chadsansing]

We should:

• Consider the taxonomy of open projects and their domains' needs from a document like this.
• Develop 3-5 use cases that might address those needs.
• Identify internal and external partners who might test those use cases.
• Document those tests and use them to improve the framework.

from a conversation with Allen Gunn

[chadsansing]

Would like to involve internal and volunteer communities like MCWS and MDN in addition to external partners. Perhaps drawing 3-5 testers from:

• F/OSS.
• Open Data.
• OER.
• Open Science (as the 5th since we have a lot of this DNA in the project already).

[chadsansing]

We might develop use cases like:

• Long-form self-assessments.
• Short-form self-assessments.
• Long form planning canvases.
• Short form planning canvases.
• Long form post mortem surveys.
• Short-form post mortem surveys.
• Fellows training.
• Short form applications surveys.

cc @Saallen

[Saallen]

I would also suggest we use the new personas as an initial testing and conversational piece Lopping in @xmatthewx who can point you to the latest version

[chadsansing]

+1

[xmatthewx]

Great idea. Thanks. Draft personas are a PDF in drive.

We'd love any feedback on how they help and how they could be more helpful.

[chadsansing]

Many thanks, @xmatthewx - more soon.

[chadsansing]

I'm recruiting leaders willing to test the following prototype use cases:

• Project design assessment
• Project post mortem
• Self-asssessment
• Applications short-form

How does this copy seem?

The ask

Stress test a use-case and write a 250 narrative about the experience - what made sense? what seemed confusing or missing? what did it make you ask, wonder, or think? was it useful? would you recommend it or use it again? how would you improve the use case?

Time commitment:** 2-3 hours

1. Read the Open Leadership Map white paper public beta.
2. Send Chad any questions and feeback you need addressd to feel conversant about it.
3. Complete the use-case survey Chad sent you.
4. Answer the tester questions about your experience with the use case.
5. Share the completed use-case and yur answes to the tester questions back to Chad.
6. Help Chad answer any questions he has about your use-case or narrative.

We would like to share the artifacts you produce as part of the OLM white paper under a CC-BY 4.0 license held by Mozilla. Is that okay? Would you like to be credited by name and role/title, or would you rather be anonymlus with a generic persona or descriptor like "director-level staffer at a non-profit" or "project manager at an open source project?"

Potential partners & ecosystem niches

• (2) OER community members
• (2) Fellows
• (1) MDN contributor or staffer
• (1) MCWS or Participation contributor or staffer
• (3) Global Spring project leads
• (3) MIT OLC project leads
• (1) Opensource.com participant
• (1) NGO staffer or community member
• (1) MoFo staffer

I'd like to reach 15 use case examples total by the end of H1.

[chadsansing]

Invite/ask revised & sent to several network/community leaders suggested by colleagues, allies, & partners; use cases shared as Google Forms; blog post extending the invitation up by Friday, 2/16/18.

• Self assessment
• Project design assessment
• Project postmortem
• Applications survey

[chadsansing]

Invites sent on 2/14; blog post published on 2/16. Deadline for testing and feedback 3/9.

[Saallen]

Hey- I have another technical tester, from MDN so will share intros over emails. I have another technical tester but who has no ties to Mofo or our strategy- would this be of interest too?

[chadsansing]

Definitely, @Saallen - thanks!

[stephwright]

How are you on testers? I see you sent out invites 2/14... do you still need more?

[chadsansing]

@stephwright, could definitely use suggestions for people from different parts of the Open ecosystem like Open Data and Open Hardware. Maybe from Carpentry?

[chadsansing]

Will gather more from fox-fooding after an April 2018 brownbag. Also added personas and before and after stories to a use-case page in the CMS site under dvelopment.

[chadsansing]

We'll test internally after meting with Mark to discuss strategy and setting up an internal brown-bag. We'll also test with 3-4 GS projects.

Self-assessment, project-design assessment, and project post-mortem have gotten the most interest, so we'll focus on improving those.

Closing.