# data[].attributes.body
I learned that simple is better and some of them will carry over into other cycles and that's okay.

# data[].attributes.body
I ended up 'enjoying' my KRs more each Cycle. As we went through the year I think I gained a better understanding of how I could better align my day to day work with overall goals for myself, my team, and other teams

# data[].attributes.body
As someone that is new to the team, I just engaged in my first KR drafting process. Initially, the process seemed a bit daunting because I am used to organizations where KPIs come from the top down. That said, after engaging in the process, I am really excited to see how it informs my strategy around coaching fellows.

# data[].attributes.body
I liked that the process kept me grounded in larger goals / more ambitious projects while not being overly prescriptive with how I spent my time

# data[].attributes.body
It helped me to stay focused on the tasks that support those KRs and make it a priority. It also helped me to recognize when cross collaborative work was needed to complete a KR.

# data[].attributes.body
I will continue to track the retention rate especially the data reflecting how many Fellows complete the course expectations by each exit marks

# data[].attributes.body
This didn't work 100%, but it gave me a way to try and prioritize tasks on a week-to-week basis to make sure I was staying on top of all of my goals to the greatest extent possible.

# data[].attributes.body
I'd like to experiment with some KRs that are shorter-term (should be Complete within a month or two) in addition to those loftier, full-Cycle type goals.

# data[].attributes.body
I learned more about being able to track data in salesforce can support understanding the KR outcomes week to week.

# data[].attributes.body
I will continue to track whether these KRs are feasible and make sure they are simple and aligned with the work I can complete within that cycle.

# data[].attributes.body
I am excited to see how my KRs change based on where my fellows are in the program. I anticipate that my Cycle 2 KRs will look different than the Cycle 1 KRs that I created.

# data[].attributes.body
I've only been here for one cycle but there were there were SO many learnings from piloting a double asynch program with new everything in LA. Enrollment deadlines, asynch “standards” and pacing. Exit points, level of engagement, AHEC, etc. will all be addressed in cycle 3 as I was able to monitor enrollment as my KR

# data[].attributes.body
Because a lot of my goals are more focused around a single endpoint and not easily measurable, I can struggle to tell whether I'm "on track." I need to put a higher priority on creating and monitoring more granular timelines for "big" goals.

# data[].attributes.body
On the front end - when you are drafting your KR(s) check in with cross-collaborators who will be supporting you with your KR(s)

# data[].attributes.headline
Strengthen post-program connections with fellows to build a deeper sense of community.

# data[].attributes.subject
Strengthen post-program connections with fellows to build a deeper sense of community.

# data[].attributes.headline
It helped keep me on task with some tasks that might otherwise fall through the cracks.

# data[].attributes.subject
It helped keep me on task with some tasks that might otherwise fall through the cracks.

# data[].attributes.body
I wanted to keep tabs on the progress and see where supports could be immediately implemented as way to track interventions.

# data[].attributes.body
It is a great tool to stay connected to the "bigger picture", working with Fellows can become individualized work but when taking a step back, our collaborations add up to the shared goal: competence and completion

# data[].attributes.body
I think my KRs need to overlap cycles to accurately track progress and improvements over time.

# data[].attributes.body
multiple people (JH, MS, KBM, AB) will need KRs related to most important milestones, not every single task.

# data[].attributes.body
It kept the focus at least at a weekly cadence on the Important work even when the day-to-day work felt flooded with the Urgent things.