Posts Tagged: Condition changes
divisionwide condition changes. The timeline was short; it's never long enough, the timing was poor; end of summer is not a good time to pull people together, and the work was a challenge; something new for UC ANR to do this at a division level, but they did a tremendous job and really stuck it out despite the challenges!
These groups have submitted their ideas for condition changes to be coded into Project Board. Katherine Webb-Martinez, Mark Bell and I have reviewed the recommendations and compared the proposed variations for the original 19 that were proposed by multiple groups as well as new condition changes that were recommended. The recommended changes were not drastically different from the original, but changes were proposed and adopted with the final list is now a bit longer, but still manageable. The next step is for a group of 12 self-identified Program Team Leaders, SI Leaders, Statewide Program and Institute Directors to work together and, using this new list plus the 2025 Strategic Vision, revise the Public Values Statements drafted back in May. I so appreciate those that have stepped up to continue this work process – not surprising given the commitment and leadership ingrained in so many across UC ANR!
I suspect this iterative process of drafting and revising is a bit frustrating for many but, as we use this information to convey the importance of your work to those who don't know us and we seek to find increased support for your work, it is important to put forth compelling Public Value Statements and be able to ‘bucket' our impacts so that the stories behind the condition changes are readily available to share with decision-makers, prospective funders, and each other. These benefits are above and beyond that which comes from aligning our work with the 2025 Strategic Vision in order to position ourselves to achieve the Vision and support our achievement with stories of how we have made a difference, even to those who don't know us. So THANK YOU to all for the commitment to the process and the enthusiasm you've demonstrated for continuing excellence in UC ANR!
Along the lines of “identify the performance objectives and then determine the design” that I have talked about previously, I've been thinking about the upcoming 2018 Position Call. Program Council has discussed the process a few times and soon we will need to have that nailed down. Below are what I believe to be the key attributes of the ideal process:
- Considers needs/gaps across the state and across program areas
- Engages clientele/stakeholders in the need identification process
- Seeks input from all UC ANR academics
- Builds recognition of needs across program areas through a collaborative process
- Results in decisions that reflect ‘hearing' academics, partners, stakeholders
- Makes it easy for Program Council to recognize high priority positions
What am I missing? Thanks in advance for your feedback!
[This article was originally published Oct. 24 in the ANR Adventures blog at //ucanr.edu/blogs/blogcore/postdetail.cfm?postnum=25473.]
Condition changes are those long-term outcomes of our work that are the evidence of how our work makes a difference. Condition changes are at a level higher than that of the personal benefit our clientele receive as a result of direct participation in our programs. Rather, the condition change represents environmental, health, or economic benefits at a societal level (e.g. improved water quality, improved nutrition and health, increased market opportunities, etc.).
How you can provide feedback
Program Team Leaders, Statewide Program Directors, Institute Directors and Strategic Initiative Leaders have worked together to develop the current list of condition changes. They will be reaching out to you to solicit your input. I would ask that you share your thoughts with those who reach out to you and they will collate all feedback they receive and provide it back through a Collaborative Tools site so that the development team can see the feedback as it is received. In early October, we will assemble all of the feedback and make decisions how to move forward.
Why this is important to you?
The final list of condition changes will be coded into the new Project Board (UC ANR program information system that will be replacing DANRS-X and integrated with the merit and promotion process for UC ANR academics. We will be asking academics to assign a percentage of time you spend working towards the condition changes. This will replace assigning your FTE to the federal Knowledge Areas. In addition, you will be tagging condition changes to your work when you write your outcome/impact narratives. You will be able to tag multiple condition changes to a single narrative provided you have quantitative evidence of the effected condition change.
How will this information be used?
The condition changes will be used in multiple ways. First, the condition changes and aggregated effort associated with each condition change will be used to determine if we have sufficient capacity working towards the changes needed to achieve our 2025 Strategic Vision. This will help guide future investments by UC ANR and help you, as an individual, identify priorities for directing your own effort. Second, the outcome/impact narratives that are tagged to specific condition changes will provide us the evidence needed to share all of your good work with supporters. The condition changes will serve as a sorting mechanism for the outcomes/impact narratives. The narratives themselves provide quantitative evidence of your outcomes including how they contribute to condition change indicators, as well as frame the work (what was done, where, why, who were the partners, etc.). Because of the intended uses of the information, it is important that we have a complete set of condition changes that represent the work we need to do to achieve our vision.
Why the rush?
The new Project Board is on track for roll out in March. In order to have the condition changes be part of Project Board and not a separate, additional reporting request, we need to have them coded in the system. The development team has indicated that they need the information in early October. Therefore, we are requesting that all Program Team Leaders provide their collective feedback (1 document per Program Team) by October 1. We will review the feedback, draw up a revised list of condition changes, and have that turned around to the Project Board team quickly.
What happens after the feedback is provided?
We will continue to talk about condition changes and condition change indicators throughout the fall and into spring. We are planning to offer training in the winter and spring to address condition changes, condition change indicators and how they tie to Public Value Statements that are currently in draft form. The Public Value Statements will be reviewed and modified yet this fall. If you have interest in being part of a small-ish group that will review and revise the Public Value Statements, please let me know via email. Note that condition change indicators and public value statements will not be part of the reporting in Project Board or any other form; only condition changes will be reported against in Project Board.
Tips to consider
- Condition changes must be measurable; condition change indicators are the metrics used to quantify the magnitude of change in a condition
- Condition changes should not be audience-specific but rather apply to any/all of our audiences as appropriate
- While I am an incurable ‘lumper' it is best to be a ‘splitter' when it comes to condition changes because it provides greater clarity as to what the evidence that support change really is and will allow for improved aggregation of your impact stories making it easier to share your work with others (easier to find, easier to understand and convey appropriately).
- Having more, rather than fewer, condition changes in Project Board will not cause you to have to report the same thing in multiple locations – the coding is planned to provide opportunity to use multiple tags for the same report.
A generic logic model used for reporting to USDA National Institute for Food and Agriculture can be viewed at http://ucanr.edu/sites/anrstaff/files/270919.pdf.
Associate Vice President