# data[].attributes.body
Work through any assumptions that immediately come to mind and try and identify the root cause of them. Is it truly because I do not fully understand the why, or is it because I am resistant to the additional work that comes along with learning something new.

# data[].attributes.body
When I think of "hard" changes, I think of how impactful it is to people. Having empathy for all the different ways the change can impact a person is challenging.

# data[].attributes.body
Initial response is sometimes anxiety and self-sabotage. Practice reframing interpretation of the change to ensure full comprehension and focus on alignment champion for team.

# data[].attributes.body
act quickly on it but also setting up periodic check-ins because easy change usually tend to be missed after a while if not being checked in

# data[].attributes.body
Ensuring that cross-team dependencies are clear and managed properly before acting

# data[].attributes.body
Focus on the goal of the change and identify any existing barriers for me to adopt the new process or motion.

# data[].attributes.body
Think of how the change will impact other team members and provide them guidance on how to manage future expected outcomes.

# data[].attributes.body
Again, I’d need more clarification. Usually, a couple of sessions with my manager, stakeholders, and peers help, but I also need some time to digest, reflect, and get ready to embrace the change.

# data[].attributes.body
expolore the change and try to embrace it, but adoption can be slower. Make excuses.

# data[].attributes.body
I usually need some clarification before I can jump in. A quick chat with my manager usually helps me get started.

# data[].attributes.body
Take a bit more time to understand why & align on messaging with my manager or fellow leaders.

# data[].attributes.body
When there is a difficult change, or a change that seems difficult, I find it is both critical and difficult to separate all other ongoing tasks from the impacts of the change in order not to get overwhelmed.

# data[].attributes.body
Usually just jump to execution. There isn't really need to gain alignment with others.

# data[].attributes.body
Champion change across the team with enthusiasm

# data[].attributes.body
Quick to identify next steps & rally team alignment

# data[].attributes.body
Dive in head first and adopt.

# data[].attributes.body
Remembering that easy changes will still require change management on a different scale than large ones. Perhaps more 1:1 check ins and reinforcement of expectations to ensure everyone is still on the same page

# data[].attributes.body
I usually need to step back, consult others, gather my thoughts, and make a decision before completely buying into the change. Over time, I find that I do transition easily to become a supporter, but it does require more explanation and rationale behind the decision before I can be a supporter.

# data[].attributes.body
I tend to get right to it, skip to the experimenting phase, seeing how this new change will effect my day-to-day at work.

# data[].attributes.body
Think thoughtfully about the change. Ensure it makes sense. If it doesn't, try to find the gaps in the decision or my understanding. Once it makes sense (hopefully), move to aligning others.

# data[].attributes.body
Overthink the possible negative outcomes and sometimes hesitant to act trying to think of a variety of potential solutions.

# data[].attributes.body
Embrace the change and act on it right away. If there are tasks that need to be completed, action on them right away to get them out of the way.

# data[].attributes.body
Pause first to understand the purpose for the change as well as steps and relevant context. In most cases, easy change leads to easy adoption, but I try to avoid getting ahead by skipping steps or not getting the whole picture.

# data[].attributes.body
Focus too much on the complexity and not enough on the benefits.

# data[].attributes.body
Able to move without hesitation and get onboard relatively quickly once I understand the why/how.

# data[].attributes.body
It takes me a while to come around to the change. Typically I need time to process and think through why something needs to be changed, and see the logic.

# data[].attributes.body
Take quick actions, like updating documentation, links, and other assets that are impacted by the change

# data[].attributes.body
Quick to acknowledge, understand, and action on in my day-to-day. Typically, a positive or active supporter with limited questions or explanation needed.

# data[].attributes.body
pause and start thinking about the reason behind + drafting a plan to break down steps to take to adapt

# data[].attributes.body
Anxiousness

# data[].attributes.body
Forget to think about the long term positive affects, jumping right into what the challenges will be in the short term or what can go wrong

# data[].attributes.body
What words, feelings, and reactions come to mind when you think of easy vs hard change?

1. Click the + sign under the heading

2. Add your response to the question

3. Comment or like other posts

# data[].attributes.body
EXAMPLE: Avoid implementing - analysis paralysis

# data[].attributes.body
EXAMPLE: Jump right to action without asking enough questions