team building

Passing the Torch of Positive Leadership

by at


A month ago, I announced I was leaving Temple after five years as VP and CIO. The outpouring of appreciation and well-wishes has been overwhelming and wonderful.  
The thing that I am most proud of during my time at Temple is the deliberate crafting of an empowered and positive work culture. This was a team effort with many people stepping up to help. 
The HR development team created and delivered the “Wiser Way” leadership training that taught common language with concrete tools to improve communication and habits. A self-nominated team developed the mission and later formed the culture committee that included me and our HR partners. A recognition committee developed the “Cheers for Peers” program. We dived into DevOps and Agile practices. We read and discussed books. We created “Wonderful Wednesdays/Whenever” to foster innovation and uninterrupted work time.
Here are a few of the comments from team members about the impact of these cultural changes.

“You’ve lit a spark and set things in a new direction. You’ve made a difference in so many ways starting with ‘seeing’ your staff and other Temple colleagues and encouraging us all to ‘see’ each other, too.” 

“I just wanted to say THANK YOU for everything!  ITS culture is more open-minded, more empathetic, technologically more forward-thinking, and it feels like our collective self-esteem is reaching upward.”  

“You’ve made a profound impact on my professional and personal life through your leadership and example of strength through vulnerability.”  

One colleague cited the book “Stewardship” by Peter Block and the value of service over self-interest. The sentiment summarizes the lasting impact that I and so many leaders in our organization desire to have.

“The book says that ‘Stewardship is to hold something in trust for another. It is the willingness to be accountable for the good of the larger organization or community of which we are a part, by being in service to, as opposed to in control of, those around us.’ I think the way you carry yourself, ‘leadership’ could directly replace ‘stewardship’ in that quote. You truly have left us in a notably better place than when you arrived on many levels that are not articulated by data and statistics. Now it’s up to us to make sure we continue the momentum and example you set. I believe that measure is the simplest yet most important aspect of successful leadership.”

I am now passing the torch of positive leadership to the Temple ITS team. Will the culture that we created together continue to thrive and improve?  I am leaving it in your capable hands.
 

Communicating when leaders make poor decisions

by at

As a cost cutting measure, I made the decision to eliminate Slack. It seemed like Microsoft Teams had the same functionality and I was hearing from several people that we had too many tools and needed to simplify. After making the decision, there was a groundswell of concern from the teams that were using Slack. 
After hearing the concern, I turned to my culture committee. This is a group of thought leaders from across the organization that I have been meeting with weekly. They have been helping to shape our culture and I know them very well and trust them explicitly. Every single one of the committee members expressed why they thought my decision was a poor one and how the tool was helping coordination and communication across teams. Based on that discussion, I reversed my decision.  
After talking about my decision and subsequent reversal at our all staff meeting, I got the following email from Michele Schinzel, which I am sharing with permission.
===========================
Hi Cindy, 
First off, thanks for hosting the All Staff meetings, which allow us to talk together, and voice as much (or little) as we wish. 
Hearing that there were discussions to do away with Slack, I wanted to give another cheer of support for the product.  So, for what it’s worth, I thought I’d share my Slack story with you. 
I joined Slack on January 10, 2019.  Immediately, I received a silly animated gif from someone, welcoming me.  Rolling my eyes I thought, “Just what I don’t need.  A Facebook for work!”  Many months later….  I still felt that way.  I did not see the benefit, and it seemed like another thing to have to remember to keep up with. 
Time rolled on.  The channels became organized, and more people joined.  My team made a group to use for communication.  I checked in to see what was new on the “Random” channel.   Then I found myself wanting to see a new article, or a picture, or a quiz.  Gradually, other benefits became evident.  Such as….

    • Some teams built workflows into their channels.  These Slack workflows allow for quick requests of a team, with clear communication throughout.  The Portal team, for example, has a short form we can fill out when we need them to move code from DEV to the PRE portal.  I can see every request by anyone.  Fantastic!
    • Throughout the COVID experience, I’ve been reading the Helpdesk Slack channel.  They post questions and solutions quite regularly.  There are useful stats and notifications when calls are higher than usual on a certain service.  Impressive.   
    • Recently, when a certain database went down, several groups chimed in on the DBA Slack channel to confirm the finding.  It was addressed.  Now that we’ve had the correspondence, the history is all searchable.   A quick search showed a similar conversation just one week prior.  Hmmm.
    • I’m learning a little about teammates that I never had a reason to meet. 

MS Teams has its use.  I’m a member of 20 teams in Teams, and many of those Teams contain sub-channels.  When I want to work on a project, I look at Teams.  I don’t usually seek out updates, and I tend to only post information following a meeting.  The good part is, it’s all in one place, and we can tag one another with tasks. 
In the end, my view is that Slack stands out as a collaborative communication tool, and Teams is a project organizer.  Could our favorite Slacky features be fit into Teams?  Maybe. 
Slack seemed like a ‘Facebook for Work’, but silly gifs aside, it keeps us connected in a fun interactive way that we are naturally drawn to.  I WAS a doubter of Slack at first, but now I love it.   I wouldn’t have written this otherwise. 
Thanks.  
-Michele
Michele Schinzel | Assistant Director Systems | Banner Document Management | Temple University
==========================
When I received Michele’s email, it confirmed to me that the reversal of the decision was the right thing to do. However, it made me pause to reflect on why I didn’t reach out for feedback before making the original decision. There were several reasons why I didn’t. 

    • The decision was made in a budgeting meeting with the upper management team under extreme pressure to cut our budget. 
    • I had gotten feedback at our all staff meeting that we had too many communication tools and should reduce the number. 
    • I had a bias against Slack because the couple of times I attempted to use it, I found little value and had stopped using it.

The bottom line is that as a leader, every decision you make is with partial information. Recognizing that and being open to adjusting decisions when you get more information helps you avoid analysis paralysis on one end of the spectrum and obstinate defense of decisions on the other end.
I am very grateful when individual team members openly share their experiences and concerns with me. Receiving this kind of feedback as a leader is like gold. 
A couple of questions to ponder this week:
Is there information that your leaders need from you that could help them make or alter their decisions? 
As a leader, how do you react when people give you this kind of feedback?

Supporting team members who have ideas for improvement

by at

“Dreaming and Doing” by Sam Howzit is licensed under CC BY 2.0


One of the foundational practices in DevOps and Agile is to support team members who have ideas for improvement. This is difficult to do because we have a lot of work to get done and trying out new ideas creates more work. When the idea crosses organizational lines and normal job duties, it is even more difficult to take action. We have implemented Wonderful Wednesdays as a way to give time to explore ideas and practice creating self-organizing teams. A recent example reaffirmed to me why this practice is so important, especially when you are trying to transform the way that your team works.
Like most organizations, we have a help desk with software that we use to track all of the requests for support. This software is managed by the help desk team. One of our new help desk team members, Dominic (Dom) Malfara, was looking for ways to be more efficient in updating the software. He wanted to be able to upgrade the software in the middle of the day and be able to quickly recover if any part of the system went down. He reached out to our infrastructure engineering team, who were investigating how to use Kubernetes containers to automate and modernize our server environment.
That team embraced Dom, recognizing that if they could containerize our Remedy environment, which consisted of many servers with a vendor that didn’t support containers, it would be an ideal environment to learn for the entire team. The team leader invited Dom to the team’s daily stand-ups, Trello board, and Teams channel. Throughout the project the entire team was inclusive and accommodating. Despite org chart lines, Dom felt like he was part of their team and it was exciting working towards a goal with them. The infrastructure team reprioritized their work and helped Dom identify all of the layers of systems and management tools needed to fully automate and containerize the Remedy servers. 
This took several months and required full support from the leaders on the help desk and the infrastructure engineering team. Doing this required more time and more people than a traditional upgrade of the Remedy servers. It required making the time to experiment. 
Dom was successful in containerizing the Remedy environment. It did not go perfectly.  We had a bit of user interruption throughout the day as we made the transition. Through the problems, the help desk leadership team didn’t yell or blame anyone, but instead asked what they could do to help. Various team members posted screenshots or descriptions of things that were broken, allowing Dom space to focus on calmly fixing things so they would not happen again.
The results have been everything that we hoped for and worth the investment of time. We halved the needed hardware. Upgrades are now done by building parallel environments which mean we can fully test the new production environment and roll over and back between the old and new environments in seconds. All the hard work now occurs up front, and not during a maintenance window where people are prone to rush/make mistakes. Because the work is now automated and reproducible, bringing up a new test environment takes minutes instead of days. We can monitor the system load and scale instantly when needed. 
A couple of weeks after the transition was done, Dom did a presentation during Wonderful Wednesday teaching others across ITS. I went to the presentation and was in awe of the amount of learning and technical knowledge that was required to make the transition. It was one of the highlights of my year.
Thanks to Dom raising his hand and the infrastructure team fully supporting him, we have a roadmap on how to make the rest of our infrastructure more efficient, modern, and scalable. As a leader, it reinforced to me how important it is to support those individuals and teams who raise their hand and give them the time and resources to learn and make your organization better.
Here are my questions for you this week.

  • How do you support individuals who raise their hands with an idea? 
  • How do you treat others who come to you with an idea that requires you to change what you are doing? 
  • Is there a project you are working on currently that someone could collaborate with you for mutual benefits if they only had some way of knowing about it?

===============================================================
Epilogue: As part of the process of writing these blogs, I always ask for feedback from the people who are mentioned in the blog. I wanted to include this email from Dominic to me about his view of the experience.
Hello Cindy,
Thanks for sharing, I just wanted to share some quick notes on the overall experience because it was really special to me. Our self-formed team was definitely influenced by all of the changes made to the culture and how ITS members are reacting to that: 

  • Wonderful Wednesday allowed me the freedom and time to invest in pursuing something innovative instead of doing things how we always have, WW got me quick buy-in from Jim and Paul because instead of battling with scheduling time to prove value in something and how it prioritized with our other work, I was able to use that reserved WW time to learn skills and proof of concept this project. I was excited to work on new technologies and make life better for us and that energy didn’t go to waste having to meet and debate and formalize things. Natural experimentation took its course and we got to follow an informal guideline of what we wanted to accomplish and how we were going to do it
  • Slack/Teams promotes open communication across the organization so it is now commonplace to talk to others in ITS, I get to interact with members of IT that I might not even meet otherwise. Help or knowledge with something is a message away, and with group chats I get visibility into what people are working on, instead of knowledge being hidden in email chains that I wasn’t CCed on or meetings I wasn’t a part of (the all-staff meetings, summits, and What’s New newsletter all influence this as well). I heard that Infrastructure Engineering was already exploring Kubernetes and we got to learn that together.
  • Leaders like Jorj, who doesn’t have a reporting relationship with me, but acted as a strong mentor and helped break down any barriers I faced along the way anyway. People like him that are genuinely interested in the technology and making Temple a better place are really inspiring and I hope I can pay that forward and influence those around me

Thanks again to Jorj for all his help and mentorship, and to you for the culture you are creating in Temple ITS! This project wouldn’t have been possible without it. I have learned a lot of valuable career skills and the failures/mishaps along the way that gave me real world lessons and I honestly had fun doing it! 😄
Thanks again, 
Dominic Malfara

Reframing Frustrations to Facilitate Difficult Conversations 

by at


Last week at our planning retreat, I wanted to make sure that the leadership team was able to talk openly and constructively about some chronic problems across the teams. I found an exercise from Mark Gorkin that helped do this in an amazingly effective way.
Before we started the exercise, I wanted to shift the way that people thought about frustration. In The Enemy of Engagement, Mark Royal and Tom Agnew assert, “The more loyal and engaged employees are, the deeper their frustration will run in the face of obstacles.” So instead of labeling frustration as bad, we labeled it as a sign of the most engaged and loyal team members. That made it okay to express the frustrations because it meant that you cared deeply and wanted to make things better.
With that framing, each person took a few minutes to identify sources of everyday workplace stress and conflict or to list barriers to more effective and creative team coordination. At each table, we spent ten minutes sharing our frustrations. Then came the creative and team building part of the exercise. We asked each table to draw their frustrations. They could make as many posters as they wanted in ten minutes.
Everyone jumped in with both feet. The teams were working together intently around their posters and there was a lot of positive energy as the teams brainstormed about how to communicate their frustrations in a visual way.
After everyone was done, we created a gallery and everyone looked at all of the posters. Then each group got a chance to explain their drawings. After the explanations, we took some time together to dive into the problem and talk about possible ways to make it better. 
It was intense and uncomfortable.
And very productive and necessary. 
We had conversations about frustrations that spanned years. Information and background was provided that gave the individuals and teams perspective and insight they didn’t have before coming into the room. 
After talking with several different participants immediately after the exercise ended, I discovered that several people thought that getting into the specifics in a group setting felt like blame and was inappropriate. After discovering this, I immediately facilitated a discussion with the entire group about how we could have these difficult conversations with details without blame. Many people indicated that without specifics, the problem was theoretical and not clear. Through the exercise and discussion, we established norms about how we would talk about difficulties that allowed us to get to the specifics.
We still have room for improvement, but this exercise was a good way to prompt and practice having difficult conversations.
What have you done in your teams to hold difficult conversations that are healing and helpful?

Creating a safe learning community

by at

“What does respect mean to you?” by retrokatz is licensed under CC BY-NC-SA 2.0


I am teaching a leadership class at Temple for the first time. Since I agreed to teach the class, I have been vacillating between anxiety and excitement. It is definitely outside of my comfort zone and I have been worried about whether I am good enough. Since overcoming feelings of inadequacy and stretching has been at the heart of my leadership journey, I realize that I am not only the teacher, but this is an incredible opportunity for me to learn how to be a better leader.
The first class was one of the most amazing experiences of my life. After a quick summary of the structure of the class, I asked the entire class how we could create a safe learning community. Using the 1-2-4-All Liberating Structures, we established as a group how we would act and support each other on our growth journey. The list that the class created together was more comprehensive and better than the list that I would have created. They wanted to be able to be open and vulnerable and know that others would listen without judgment, as we practiced living the leadership principles that we would be learning.
Then we spent the rest of the class getting to know each other by telling our core stories. We arranged our chairs in a circle and each of us shared three core stories from our life and what we had learned from those experiences. 
Several people in the group got emotional, including me. We were sharing deeply about our struggles and our ability to overcome those struggles. We talked about health challenges, close relationships, death of loved ones, physical injuries and having to give up our identities of who we thought we were when unexpected challenges arrived. 
It was one of the most powerful experiences that I have ever had. There was so much wisdom and leadership in that room that had already been developed. I was reminded again that leadership is not about telling others what to do, but about creating an environment where the best ideas can surface and be shared.
At the end of the exercise, we talked about how differently we felt about the people in the room and the implications for leadership and life. As I was leaving the room, I realized that I don’t necessarily know the core stories of the people that I work with on a daily basis, and I am not sure how to do that in a safe and non-invasive way. 
I would love to hear about how you have created safe learning communities.
 

Best books about creating transformational organizational change

by at

“Inspire Change” by Brian Solis by The Brian Solis is licensed under CC BY 2.0


I love to read and am always looking for an engaging book. One of the ways that I deal with my daily commute is to listen to audiobooks, which has augmented and somewhat replaced reading physical books, which is my first preference, or ebooks, which I do for convenience, especially when traveling. My friends and colleagues know about my insatiable appetite for good books and so regularly send me recommendations. 
At work, I have been on a quest to create a high performing culture and have used books to help make that transition. Recently, Primed to Perform was recommended to me and it is my new favorite organizational change book. I have been recommending it to anyone who will listen and even gave it as a birthday gift last week. 
The premise of the book is that you need to promote both tactical and adaptive performance to excel. Most organizations focus almost exclusively on tactical performance. What I love about this book is that it combines a whole bunch of research about personal and organizational change management, and puts it into an easy-to-understand and measurable model. 
The model is called Total Motivation (ToMO) which assigns weights to the reasons why people do their work. Higher ToMo scores are directly correlated with the success of an organization. It is an elegant theory that incorporates many of the positive business principles and gives a way to measure how your organization is doing in creating a culture that is high-performing and fun. There is a great talk by the authors at Microsoft Research that you can view here.
We will be using this book this year as we continue our change in the Temple Information Technology Services team. We have already taken the group ToMo test as a baseline so that we can measure whether we are making progress in creating a more higher performing group.
Here is a list of some other books that have been very impactful as I have studied how to make deep change in organizations and myself.

I would love to hear your recommendations to add to my reading list. What books have been impactful to you on your leadership and organizational change journey?

Creating Momentum for Organizational Transformation

by at


The IT world has been shifting drastically. Everyone knows about cloud computing, but most people do not understand that the way software needs to be developed to be truly cloud-based, is substantially different than how software has been built for decades. Quick development cycles and continuous updates to software are now required. To make this shift, some organizations are transferring the LEAN operational principles that propelled Toyota to produce high quality and reliable cars to software delivery. In software development, the LEAN principles are referred to as Agile Development or DevOps.
LEAN principles can be effectively applied to almost any process to make it better. The main idea is that for work to happen in the fastest possible way, it needs to flow through the system continuously without stopping and not come back into the flow of work because of poor quality.  To integrate these principles requires a transformation in how an organization acquires and builds software and the infrastructure to support it.
The challenge is how to create enough energy and momentum within your organization for this transformation.
To introduce Agile and DevOps practices within ITS at Temple, we have done several things to increase the awareness, understanding, and support for this transformation.
We looked for experts. My leadership team went to visit Pivotal, a company that trains organizations on how to make this shift. After that visit, we sent several team members from different parts of the organization to the SpringOne conference, where Fortune 25 companies who have adopted the Pivotal methodology and tools converged. The team came back energized and awed by what they saw and excited about what we could do. The conference also helped them understand that this shift is not about technology, but about people.
We spread the word. After these evangelists started talking to their teams about what a difference DevOps could make at Temple, we sent 27 attendees to a local one-day DevOps conference. The participants came back with a better understanding of the principles of DevOps. They were also encouraged that other organizations were struggling with how to apply these changes as well, understanding that we weren’t as far behind as we feared.
We started experimenting with the principles. My leadership team made a Kanban board of our work across the organization to try to get an understanding of our work in progress. The visual display of our work traffic jam was powerful. Although I have been studying these principles for years, this exercise drove home to me that I had not done my job of focusing our teams on the most impactful work for our organization.
We invited everyone to participate. We announced a retreat to develop the strategic vision for how ITS could adopt Agile/DevOps principles. Everyone was invited. The only requirement to attend was to read “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win.” Several people commented that although it was fiction, it accurately described how we feel overwhelmed as we juggle the unending stream of requests and the unplanned work that happens when things break.
Over eighty people came to the retreat and it was an energizing and productive day. We created a shared vision for Agile and DevOps at Temple, learned about the principles together and brainstormed ideas about how to move the culture and operational change along. This is the shared vision for Temple ITS that the attendees created at our retreat.

Culture
We are educators, who support an inclusive environment that is respectful, people-focused, and fun!
We encourage learning and recognize people’s positive intent. With trust, we grow from our mistakes by continually supporting a quality improvement mindset (LEAN principles).
Innovation
We strive to be innovative in technology, cost efficiency and creativity. We advance our mission by creating opportunities to explore improvements and expand our personal development. We lead by supporting a rapid development environment.
Optimization
We optimize our time by identifying and automating repeatable processes to efficiently utilize our technical resources. We seek to minimize redundancies, rework, and defects to strengthen our resolve to follow LEAN principles. We use agile processes and choice architecture to present different alternatives in process and user experience to our customers.
Collaboration and Communication
We operate everyday with clear communication, collaboration and information sharing. We build and foster all of our relationships by inviting internal/external stakeholders to be a member of our team and encouraging feedback with authenticity in our discussions.

We have already instituted changes with daily leadership stand-ups, created Wonderful Wednesdays to encourage innovation and experimentation and started to visually track our work. As we head into a new year, we have so much energy about the possibilities, and the really wonderful thing is that the transformation is being championed by the group and not just me.
I can’t wait to see what the new year brings!

Playing together builds teams

by at


Annual Temple Tech Olympics – Photograph by Michele Schinzel


We just held our second annual Olympics for Temple Tech. It is a time for our team to step away from normal work and play with each other in a relaxed setting. The day is organized by volunteers and is funded by my office. What a great investment in building our team. It was such a fun day!
This year we had better weather and more people came out to spend time playing games, eating, and socializing. Last year was our first time holding the event and many people did not attend because they said they did not have time. The fact that more people came was an indicator to me that it was more acceptable to attend this kind of event and step away from our normal work.
I spent the entire day at the event signally how important I believe playing together is in building relationships and teams. It was wonderful! I personally participated in the cornhole tournament and played volleyball, scrabble, and bananagrams. I was able to catch up with team members from across the organization and heard about family vacations and adventures outside of work.
The relaxed setting allowed several people to personally thank me for the impact that my style has had on the group, which I appreciated.
My favorite encounter was with Jay Holt, who shared his incredible experience skydiving, which he credited to the Wiser Way training that we did as a group last year. He talked about wanting to make stepping outside of his comfort zone a regular habit and that skydiving was his first big step toward doing that.
Our jobs in IT are stressful much of the time because we help people who are experiencing technical problems, have an inexhaustible demand for our services, and run the systems for the entire university that need to be available all of the time. We work in teams solving problems and getting projects done all of the time, so we are used to working together and enjoy solving problems and building solutions that serve our students, faculty and staff.
Playing together is such a delightful break from the normal interactions that will strengthen our ability to work together under stressful situations. It builds connections and stronger relationships, gives everyone a needed break, and promotes having fun at work. As we wrapped up the day, the planning group was already talking about what they will do next year to make it better and my leadership team was talking about how to encourage more team members to take a break and join us.
 

Changing Lives through Tech Training

by at

Jamal receives his diploma upon graduating from the Temple Tech for Philly program.
Photography By: Marissa Weekes Mason


Earlier this month, I attended a graduation of 14 adults who completed the first step in the Project Home/Temple Tech for Philly joint program designed to give people, in the neighborhoods that surround Temple, marketable technical skills so they can change their lives for the better.
Project HOME is a Philadelphia non-profit organization empowering individuals to break the cycle of poverty and homelessness through affordable housing, employment, health care, and education. Temple University started as a night school in the Baptist Temple as a way to improve the economic situations of the laborers in the surrounding Philadelphia neighborhood. That story is core to the purpose of Temple; to find and polish the “acres of diamonds” that are in our backyard. I came to Temple because that purpose resonates strongly with me.
The idea for the program sprouted over a year ago when we met with the Project HOME IT team to discuss whether there was any need for some of the refurbished computers from Temple for Project HOME residents. As we talked about their needs, it became clear that we couldn’t put computers into the neighborhood unless there were trained technicians who could service them. It also became clear that teaching marketable job skills would have a much larger impact than distributing computers.
Erich Smith from Project HOME and Jonathan Latko from Temple took the idea and ran with it. They designed the Tech for Philly program to give participants concrete technical skills and experience. The first step is 10 weeks of intensive study learning how to configure, support, and repair Windows computers. The second step is passing the CompTIA A+ certification exam. For participants who successfully complete the first two steps, the final step in the program is an internship at Temple to get hands-on experience and training. Project HOME provides the connection into the community, facilities, and funds to pay the participants for their time. Temple provides the equipment, instructors, and internship opportunities.

The first graduating class from the Temple Tech for Philly program. Photography By: Cindy Leavitt


A lot of thought and effort went into recruiting and selecting participants who had the aptitude and desire to learn. The program requires incredible commitment from the participants.
I volunteered to co-teach two classes on networking. My co-instructor and I struggled about how to cover all the concepts that the participants were expected to know in the few hours in class. Other instructors said that they had the same struggle. This meant that much of the learning was left to the participants outside of the class time. In addition to lots of reading, the participants got to practice what they learned on computers they built for themselves using refurbished parts from the Temple computer recycling program.
The sense of accomplishment and joy was inspiring to watch as the participants received their diplomas. They had worked so hard and were proud of themselves. An especially touching moment was when the graduates presented a computer they had built to the lab manager as a thank you for the many hours he spent helping them learn.
Without exception, everyone from Temple and Project HOME who had attended the first meeting came up to me at the graduation to marvel at the outcome of that initial outreach. And the instructors talked about how much they enjoyed seeing the intense desire to learn from the participants and how meaningful it was for them to be part of their journey.
When we are involved in transformational learning, whether as a student, teacher, or organizer, it changes our lives for the better. It gives me great satisfaction to be a small part of this program.
How can you be part of transformational learning in the coming year?
 

Getting others to join the ride

by at

Biking in South Island New Zealand


Several weeks ago, I crashed on my bicycle when I slipped on a metal strip while crossing a bridge. I was rather lucky that I didn’t seriously hurt myself. I did earn a trip to the emergency room in an ambulance and got a single stitch in my elbow along with a bunch of bruises from my hip down to my ankle. But I could walk and was back on my bike the next weekend.
When others found out about my accident, many people shared stories about their accidents or near accidents on their bikes. However, the reaction to the accidents were very different. Many people talked about how they stopped biking because it was too dangerous and drivers were too distracted and rude. While others, like me, were back in the saddle as soon as we were able.
I have been thinking a lot about what is motivating me to continue to bike even though I have been hurt and know I could get hurt again. I have posed the question to several of my biking friends. Their answers included seeking a challenge, being addicted to endorphins, biking being easier on joints than running, and loving it. They also talked about what scared them about biking and that it was a constant risk-benefit analysis about how much they push themselves.
For me, I am happy when I am on my bike. I love to be outside, feel my own power, push myself, and be with friends. So, for now, it is worth the risk.
However, I have a lot of things I do when I am biking to reduce the risk of being hurt and increase my enjoyment. I avoid heavily traveled roads, I ride where drivers are expecting and considerate of cyclists. I seek out newly paved and smooth roads. I cycle with friends who are experienced and passionate about cycling. I carry spare tires and tools for when equipment fails. I travel to beautiful and remote places to cycle.
In technology, we are constantly venturing out to implement projects or initiatives that have transformative impact. The journey to success often depends on asking people to manage change. Much of the change that needs to happen has nothing to do with technology. It has to do with how we work together and get along and whether we can get others to join the ride with us. Change is inherently risky.  Like biking, there are some people who enjoy the challenge and risk and are willing to jump right in. I know I am one of those people. However, most people want reassurance and support, because they have scars from previous change initiatives.
Over the last year, I have asked the Temple Tech team to take a change journey with me as we implemented “A Wiser Way” training to develop self-managed leaders at every level. It has been amazing to see the changes that individuals have made and the positive impact that it has had across the university. As individuals have examined their stories and shifted the way they interact with each other, our projects are being successful in unprecedented ways. We are getting things done and having fun.
As we plan our journeys, we can do many things to encourage others to come on the ride with us. Paint a picture of why a change will lead them to a better place ultimately. Make the change enjoyable. Be prepared for the accidents and setbacks that are going to happen. Give people choices. Realize that people have different abilities and speeds, so we need to accommodate training wheels and racing cycles in our plans. Make bike paths and ensure smooth roads on the transition. Develop empathy for others. Do not overwhelm individuals with too much change. My challenge for you this week is to consider how you can make the ride smoother for your colleagues as you work on projects together.