Justify the (continued) invest for an ISPO

[tfroment]

Hi, have some material related to this challenge. I am not 100% sure it is exactly the same challenge as current one : I would maybe rename it to something like "How to find corporate sponsors for an ISPO"

This material is something (mainly ppt & workshops) we already use in real situations, and we are ready to share it in Open Source (under CC-BY-4.0 license)

It covers the following topics:

• A reading grid to identify motivations and fears of a sponsors and subsequent ideas to implement in the ISPO to convince sponsors
• Motivations of a sponsor for an ISPO
• Giving a role to sponsors
• Operational actions to assign to sponsors
• Operational actions to serve a sponsor
• Blockers to corporate investment in an ISPO
• Responses to the company's blockers
• Blockers to engaging a potential sponsor
• Responses to sponsor blockers
• Expressing the value of a ISPO in terms of Corporate Value

[rrrutledge]

Is (continued) important, or should this just cover investing in an ISPO altogether?

[tfroment]

I would suggest a more generic title like "How to convince corporate sponsors for an ISPO?" (the continued is not mandatory imho since it may be considered as an obvious statement)

[jeffabailey]

Related, and we could share content depending on how we assemble the template(s)

https://github.com/orgs/InnerSourceCommons/projects/4/views/1?pane=issue&itemId=20800399

[rrrutledge]

Thanks, both!

[rrrutledge]

Hi! Glad you are working on this! Do you think that you are set to create and review this content asynchronously, or would it be useful for you to have discussion time in our upcoming meeting?

[tfroment]

@rrrutledge Maybe better if we first asynchronously share our content, then will be time to discuss it in the meeting? what do you think @jeffabailey ?

[gruetter]

Is (continued) important, or should this just cover investing in an ISPO altogether?

I added (continued) because I am in a situation where had something akin to an ISPO a long time ago which went away as a result of dried up funding. In retrospective, the primary reasons for that were that the then-ISPO had the wrong organisational home and that InnerSource was not anchored as a strategic topic for the company.

[gruetter]

Hi, have some material related to this challenge. I am not 100% sure it is exactly the same challenge as current one : I would maybe rename it to something like "How to find corporate sponsors for an ISPO"

This material is something (mainly ppt & workshops) we already use in real situations, and we are ready to share it in Open Source (under CC-BY-4.0 license)

It covers the following topics:

• A reading grid to identify motivations and fears of a sponsors and subsequent ideas to implement in the ISPO to convince sponsors
• Motivations of a sponsor for an ISPO
• Giving a role to sponsors
• Operational actions to assign to sponsors
• Operational actions to serve a sponsor
• Blockers to corporate investment in an ISPO
• Responses to the company's blockers
• Blockers to engaging a potential sponsor
• Responses to sponsor blockers
• Expressing the value of a ISPO in terms of Corporate Value

That sounds like a really interesting document, @tfroment . Sharing would be highly appreciated.

[gruetter]

Here's another thought on how to secure funding for the ISPO based in the experience that acquiring and keeping on board individual sponsors can be challenging: finance an ISPO by adding a percentage to the fee that users of the collaboration platform in question have to pay anyway. That way, everyone would have to pay and existing financial structures can be used.

[tfroment]

This content is actually part of a huge doc () we have in our base, I am preparing an extract to be shared here so that we cover specifically the topics I was talking about. Stay tuned, just need to find some time :). Btw, all our content is in pptx format, so I am looking for the best solution to share them, including. versionning capabilities + making still possible for anybody to propose a contribution on them. I know Github is not the ideal place to host binary files like pptx, but I am still trying to share them on it because I really would like to benefit from "tag" / versionning AND PR features on our documentation... If you are aware of a good practice related to this kind of use case (let appart the idea to forget pptx and migrate to markdown, which we alredy considered but we don't want to because (1) this is already a framework made of 3000+ slides, so would be a huge work, and (2) our main custumers use / like pptx....

[rrrutledge]

Thanks for working and sharing, @tfroment . We do have a GDrive folder where documents can go as well.

[lenucksi]

Office 365 online does some collaboration features as well. I've never checked the versioning/named versions feature though. Slide-Program wise it is superior to Google Slides. So might want to check if there's named version history in there and then just invite people to the deck, possibly save a backup every now and then and get going. To my knowledge the "review" permission level should suffice here. Office 365 does authorized-access-through-link just like Google too.

[rrrutledge]

Hi @tfroment ! Glad you're interested in this! Is it still something that you're planning on working on, or not at this time?

[tfroment]

Hi @rrrutledge yes I still plan to contribute, did not have enough time recently but will work on it next week

[rrrutledge]

OK sounds great, @tfroment ❗

[rrrutledge]

How are things going? Will there be some update for next Monday's ISPO meeting?

[tfroment]

Hi, I finally answered to the ISC May 31 Community Call: I will prepare a presentation on this topic and share the associated document at that time. To be transparent: I had to extensively rework this document in order to make it usable in an "independent" way from the rest of our framework, and truly exploitable for someone who wouldn't have access to all the other documentation (because I extracted about 20 slides out of several hundred on the topic of value)... So to sum up: I will finalize the document by the community call and it will be an opportunity to present the context and a portion of our framework more generally.

[tfroment]

So, probable not ready for next monday (to answer your question)

[rrrutledge]

That’s no problem - it is clear that the work is moving along, which is great! We are very excited for it.

[rrrutledge]

This document focusing on how to convince people that can fund an ISPO that it's a good idea to do so.

Q: Will part of this proposal include how much can save through reuse (this is hard to collect)? A: No. There will be some examples, though. We can work on how to measure reuse.

[rrrutledge]

Hi, @tfroment ❗ Is this still something that you're working on? If not, then that's fine, but if so then we're excited for it!

[tfroment]

hi @rrrutledge , most of the content I presented in the community call (https://www.youtube.com/watch?v=_2sK7hPITDU) is extracted from it. I just need to "tune" a little bit a few slides and it will be published here

[rrrutledge]

Great! I still need to go and watch the call recording.

[rrrutledge]

I haven't seen the recording, but are there still slides that you can tune and contribute to the working group?

[rrrutledge]

Hi @tfroment - wanted to ask again about this? If it is not something that you're working on, then that's fine, too.

[tfroment]

Indeed @rrrutledge , my priorities have shifted today, and I confess that I can't find the time to finalize this contribution. Basically, everything is in my talk that I presented at the May Community event, but I don't think I'll be able to go further today due to a lack of availability. I apologize for this. Slides of the presentation at https://github.com/tfroment/public-presentations/raw/main/AdvocatingStrategicValueOfAnISPO.pptx already contains some parts of it (except cards are "png" files and not pptx format, so may be difficult to reuse them as is....)

[rrrutledge]

That’s fine, @tfroment - this community is supposed to just capture these work that we are doing anyway. We are glad for what you have share so far!