Strategic Plan Structure & Guidance for Sustainability
Explore key considerations for structuring services and functions, optimizing capabilities, addressing audiences, making cultural changes, supporting software catalogs, and moving towards sustainability within the context of a strategic plan.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Strategic plan structure, Strategic plan structure, guidance for next steps guidance for next steps Daniel S. Katz University of Illinois Urbana-Champaign @danielskatz
Questions Shaowen asked us to answer What should be the core services/functions/ capabilities that GSI should provide? How should GSI structure its services/functions/ capabilities? How should GSI allocate and optimize its services/ functions/capabilities to meet the evolving needs of pertinent communities?
But I still have more fundamental questions Who will GSI address? (who is the audience?) Software users? Software developers? What fraction of GSI addresses each?
Process Questions How do we try to make cultural changes? Cultural changes to support developers and their work Cultural changes to lead to better community behavior, aimed at users Where do these cultural changes get applied? Institutions? Publishers? Societies? Funding agencies? Can we shift from today's practices, to minimally good practices, to good enough practices, to best practices
Software catalog? Should GSI support a catalog of relevant software? Maybe tied to reviews and use cases? SGCI does this (collaborative community*) IRIS-HEP doesn t (not needed for HEP community*) MolSSI doesn t (competitive community*, don t want to pick winners*) Who would provide info? Who would maintain it? (*My opinions)
Sustainability Moving towards sustainability of the institute Increase resources coming into the institute Decrease work that institute has to do Encourage people to participate without funding Moving towards sustainability of software Increase resources coming into projects Decrease work that project have to do Encourage people to participate without funding Best practices Overall, increase visibility of software to decrease redundant development
Too many questions and possible activities Need to limit what we do What small number of changes do we want to bring about? What resources do we have? How can we best apply the resources to achieve the changes? Leads to formal theory of change process
Next, consider strategy Good Strategy Bad Strategy: The Difference and Why It Matters, by Richard Rumelt The kernel of a strategy contains three elements: A diagnosis that defines or explains the nature of the challenge. A good diagnosis simplifies the often-overwhelming complexity of reality by identifying certain aspects of the situation as critical. A guiding policy for dealing with the challenge. This is an overall approach chosen to cope with or overcome the obstacles identified in the diagnosis. A set of coherent actions that are designed to carry out the guiding policy. These are steps that are coordinated with one another to work together in accomplishing the guiding policy.
