Category Archives: Nadyne

Elpha: “Leading an effective design organization”

Elpha invited me to write about leading an effective design organization. Here’s what I had to say:

Leading a large organization is a hell of a job.

Sometimes it’s fun and exciting, like when you get to invest in a big project to imagine a new future for healthcare that’s built around the real-world needs of people no matter their socioeconomic status, ethnoracial identity, gender identity, or the intersection of those.

Sometimes it’s empowering, such as when you get to address pay disparities by ethnoracial identity and gender identity within your company.

And sometimes it’s infuriating, like when a peer executive writes off your entire organization’s work as “futzing about with pixels”.

Throughout my career, I’ve established brand-new teams in user experience and design, scaled teams, and led large global organizations. I want to share with you some of what I’ve learned about how to effectively lead a design organization as an executive.

What does it mean for a design org to be effective? To me, it means three things:

  1. The design org has a shared purpose and vision where everyone is empowered to do their best work, there is a lot of support for growth, and high performers are rewarded for their contributions.
  2. Our cross-functional partners know the value that design brings to the products and services that we create and grow, help us ensure that we’ve got what we need to do our work, and hold us accountable for delivering high-quality business results.
  3. We understand both the needs of our users as well as our business objectives and bring them together in a unique way that creates new value.

Each of these three points needs careful tending by the leader of the organization. A shared purpose and vision can feel like it’s been thrown aside, especially during times of uncertainty like our current economic climate. A change in leadership can result in new cross-functional partners who no longer understand the value of design or ensure that design has sufficient resources to be effective. As user needs and business objectives evolve, we have to understand that change and evolve alongside so that we can continue to create new value and not be left in the dust.

Getting all of this right is especially important, and can be especially hard, because design is one of the organizations within a company that has a higher-than-average number of people from historically-excluded backgrounds. We have more people of color, more LGBTQIA+ folks, and more women than many other organizations in a tech company. The diversity of the design team is one of our greatest strengths as we work to build products and services to meet everyone’s needs. However, we’re more likely to have the value of our work questioned or to have our leader under-leveled compared to the leaders of our cross-functional partners. We have to fight not only to have our seat at the table. I’ve learned that getting a seat at the table is only the first step: everything that follows is about using that seat effectively to meet business objectives, meet user goals, and be an effective advocate and ally for historically-excluded groups.

As a design executive, I rely on three things to help me see my way through all of this:

  1. Empathy. In addition to empathy for our users which is one of the most common traits and the best part about being in user experience, I extend my empathy to my cross-functional partners and fellow executives. By better understanding their perspectives, their needs, and their constraints, I’m better able to bring everyone along to reach better decisions.
  2. Love of my craft. I’ve been in user experience for over 20 years. I still love everything about it, from doing the early discovery work before we have product-market fit to understand what needs we must meet, to delivering a product and continuing to iterate on it to make it better meet those needs and whatever new needs emerge. As a leader, I get to create opportunities and remove roadblocks so that the folks who report to me have the space to love their craft and deliver their best results.
  3. Business acumen. By developing a deep understanding of our business environment and objectives, I can align the design org to the most important and most impactful work, partner effectively across the entire company, mitigate risk, and unlock new opportunities for innovation.

managing through layoffs

Layoff. Reduction in force. Redundancy. No matter what word you put on it, a layoff is one of the hardest things for a manager to lead through. It’s natural to feel overwhelmed in this situation, regardless of whether you’re the decision-maker on who is leaving the company. You will have your own feelings about what is happening, at the same time that you’re working to support team members who are leaving and team members who are staying.

When you’re a manager in this terrible situation, give yourself grace. Take time for yourself. Invest heavily in self-care for the next few weeks. (Yes, weeks. The impacts of a layoff are long-lasting. I’m sorry.) If you’ve got a therapist, spend time with them. If you don’t have a therapist, this might be a good time for that. Whatever you do, do not dump your feelings down on your team. Don’t hide that you’ve got feelings, rather don’t dump on them. Your team needs to see you handling this situation empathetically for those who were laid off and those who remain.

While you’re giving grace, make sure to give some to your peer managers. They’re also dealing with lots of difficult things. Check in 1:1. Managers often don’t get a ton of support in a time like this, especially if their team was relatively lightly-impacted, but they’re still dealing with the survivor syndrome of themselves and their team, plus trying to figure out how to move forward. Give your peer managers some space to say the things that they can’t say to their directs, and be vulnerable with trusted peer managers too.

Whenever you talk to your Human Resources business partner (HRBP), give them some extra grace. Layoffs are terrible for HRBPs. They’re dealing with the worst of this situation. If you’ve got a good relationship with your HRBP, offer them some safe space to talk/vent/whatever.

In the weeks after the layoff, you will probably see some problematic behaviors amongst your team and others. Some folks are going to throw themselves into their work to have somewhere to channel their feelings. Some folks are going to throw themselves into their work because they’re terrified of getting laid off next. Some folks are going to disengage for a bit. Be prepared for all of that and do what you can to redirect the unhealthy behavior. If your employer has any benefits like an employee assistance plan (EAP), this is a great time to refer folks to it.

Folks are probably going to be on edge for a few weeks, or even longer. You will probably see an increased amount of interpersonal tension and stress behaviors. Be ready to manage that. Any big internal event or milestone, like a launch or review time, will probably cause more of those emotions and behaviors to bubble up. By being prepared for this, you can help divert behaviors away from unproductive or toxic ones. Many of the folks who remain might be nervous about the future of the company and whether there will be future layoffs. When you’re asked about these, be honest about what you know and what you can share with them.

You might find that your team has reduced trust in you because they believe (rightfully or not) that you must have known something in advance or must have made decisions about who to keep. They might think that you should have done more to prevent the layoff. You will have work to do to regain their trust.

This is one of the awful times of management. You can get through this.

identifying what you want in your next role

Finding your next role is a difficult but important challenge. How do you know what you’re looking for? You could simply look for your current job title, or maybe the next job title on the ladder, but that doesn’t help you know whether that’s a good job for you.

When I’m trying to figure out what I’m really looking for in my next role, I spend some time doing a deep review of job descriptions. Here’s my process:

  1. Search for jobs with relevant titles. I like to cast a wide net and look for different titles, different levels, and different size companies. LinkedIn is a great place to start for this search. Collect a good set of JDs. Don’t worry if they don’t look amazing, that’s going to be the next step.
  2. Collate the JDs into a document. Copy the text of these JDs into your favorite word processor. I insert a break or line between them so that they don’t all run together.
  3. Evaluate a JD carefully.
    • Highlight everything that you like about this JD with one color. I use yellow for this.
    • Highlight everything that you don’t like, or that raises a potential red flag for you, about this JD with another color. I use blue for this.
    • Review your good-highlighting and write out a list of what you like.
    • Review your bad-highlighting and write out a list of what you don’t like
    • Write out a list of open questions that you have after reading this JD.
  4. Repeat this process for the rest of the JDs that you’ve created.
  5. Evaluate your lists. What themes do you see emerging in each category?

When I’m first starting a job search, this exercise helps me hone in on what I really want to do in my next role. If I’m considering a role that is somewhat different than what I’ve been targeting, it helps me evaluate whether the role might still move me towards my career goals. This also helps me know what I don’t want in my next role.

After you’ve identified the themes of what you really want and don’t want in your next role, you can use that to help you rank which roles are most interesting to you. For those roles that are most interesting, you can prioritize looking through your network to see if you have a close connection to that role who you can leverage. For those roles that are the least interesting, you can decide whether you want to spend your time on pursuing them at all. Being more focused in your job search will help you manage your time and your resilience better.

the fine art of delegation

As a leader, delegation is one of the most important things to do. You have to learn how to delegate effectively, what to delegate, how to support someone who you’ve delegated to, and how to hold them accountable. As a recovering perfectionist, I’ve also had to learn how to let go of how I imagine I would do a task if I had infinite time and resources so that I don’t measure success against that.

When I’m trying to decide whether to delegate a task, and what to do if I think the person who I’ve delegated to is having some trouble with it, I ask myself the following questions:

  1. Does this task need my effort where I would (of course) do it flawlessly, or does it need someone’s effort where if they do it to even half as good as I would have done it, it would be good enough?
  2. Does this task need to have more people trained up in how to do it?
  3. Could this task benefit from having someone else do it, who might bring a new perspective or an improvement to it?
  4. Does the person who I’m delegating to need to grow skills in this area, and this task will help them grow, even if there are growing pains?
  5. Does someone else or a team need to learn that I’m not the only competent person available to them, so they have to be comfortable with the work output from other people too?
  6. Do I actually have the time to do it?
  7. Is this actually the thing that is best for me to be spending my time on? ie, what’s the opportunity cost of me doing this task?

This list helps me be mindful of spending my time in the right place, creating opportunities for others on my team to grow their skills, and right-sizing effort and expertise to a task.

evaluating the performance of managers

One of my mentees, a newly-minted director, asked how to evaluate the performance of the managers who now report to them. We were discussing some of the differences as you move from manager to director and how to make the shift in mindset.

Measuring the effectiveness of individual contributors (ICs) is relatively straightforward. Are they getting their work done? Are they helping others get their work done? Are they helping those around them build their skills and be more effective? Are they taking feedback? Are they giving high-quality actionable feedback? Measuring the effectiveness of managers, though, feels a bit harder.

Manager performance questions

These are the questions that I use to help me understand how well a manager who reports to me is performing.

How well are their ICs performing? If their team is performing well, the manager is probably doing pretty well. If their team isn’t performing well, what are they doing to turn it around? Are their ICs performing well only because, or possibly in spite of, the manager micromanaging them?

How is morale on their team? If their team is happy, the manager is probably doing pretty well. If morale is low, what is the manager doing to turn it around? Is the manager keeping morale artificially high, such as by not giving difficult but necessary feedback?

Do their ICs have the right amount of stretch assignments? Is the manager creating the right opportunities for their team to grow their skills?

How well is hiring (if any) going? Are they able to find a great slate of diverse and high-quality candidates for their roles? Are they following best practices in their hiring process?

How well is the manager working with and communicating to peer managers? This is such an important part of their job. What is the feedback that you’re getting from their peer managers?

How well is the manager communicating to their manager? Do you as their manager know what’s going on, at the right level of detail? Are you caught unaware by problems on or with their team?

Is the manager contributing to cross-team initiatives? Besides just getting the work done, you should have cross-team initiatives to help improve your organization and your company. Your manager should be contributing to these?

How well is the manager handling conflicts (within their team, between teams, between themselves and others)? Some days, it can feel like the job of a manager is only to be a mediator between conflicting parties. A good manager is managing those problems, coaching people through them to handle them better themselves, and reducing the risk that a conflict will spiral out of control.

How well is the manager assigning and delegating work? Are they giving the right work to the right members of their team? Are they doing so fairly and equitably? Are they delegating the right work from their list to folks on their team?

How well is the manager dealing with emergencies? There’s always some kind of emergency going on. Sometimes it’s work related, sometimes it’s personal, sometimes one creates the other. When an emergency of some sort comes up, is the manager handling it?

A manager is a force multiplier

What I find most important to think about in manager performance is that they’re a force multiplier. If that force multiplier is being used well, they’re likely doing their job well. If they’re failing in some aspect of their job, they could be a negative force multiplier. For example, a manager whose team is low-performing and they either can’t see it or can’t turn it around is a manager who is a negative force multiplier. It’s your job as a manager-of-managers to understand where your manager is being a positive force multiplier or a negative force multiplier, and coach them as needed.

the decisions from user research

The most recent episode of the Awkward Silences podcast from User Interviews has a brilliant interview with Holly Hester-Reilly about common mistakes that are made when planning, conducting, analyzing, and sharing user research.

When she discussed planning user research, she talked about needing to understand what decisions would be driven by the user research. This point is one that I see researchers and people conducting research miss frequently.

Knowing what decisions will be made helps you frame your research well and ensure that you’re asking the right research questions. You can always go back to the decisions that need to be made to help you evaluate whether you’re using the right research methodology or you’re applying that methodology well.

Defining the decisions that will be made as a result of the research can be a powerful tool when a team is using research for the wrong reasons. I’ve seen teams become so risk-adverse that they want to test every single thing. I’ve also seen teams become so beholden to a process that they don’t know when or even how to deviate from it. In those cases, defining the decision that will be driven and why that decision matters illuminates the more important problem that needs to be addressed within the team.

When you’ve completed the user research, you can measure its effectiveness by determining whether it actually drove the decision(s) that it needed to. This is especially helpful if you have to cut the proposed scope of a research project due to budget or timeline constraints. If your research successfully answered the question, you learned something about the benefits of a lean research plan. If it helped with some but not all of the decisions that you thought needed to be made, you can then decide what to do to address the remaining decisions to be made.

Another benefit of defining the decisions to be driven by user research is to prioritize research requests. We should invest more time in the research to support those decisions for which we have little data, or little agreement within our teams, or which have a high opportunity cost.

Knowing why you’re doing the research is at least as important as selecting the right methodology, doing a great job of collecting and analyzing the data, and sharing the results in the right ways with the right people. If you have a template that helps you plan your research studies, consider adding this section to improve the usefulness and business value of your user research.

the goal-setting conundrum

Setting career goals is hard, especially when it’s time to do it as part of the usual performance review cycle. As I’ve coached my teams through goal-setting, I’ve observed several different reasons why it can be hard to set goals. These reasons include:

  • Analysis paralysis. “I could work on any number of things, but which ones are the ‘right’ ones to work on?”
  • Future hazy, try again later. “I really don’t know what I want my future to hold, so I’m not sure what goals I should have when I don’t have a three- or five-year plan.”
  • Too much happening right now. “I’m already in a period of personal or professional upheaval and I feel like I am only barely holding on. I can’t think about the future because the present is already too much.”
  • Impostor syndrome. “I don’t think I’m actually any good at what I do today. I can’t set goals to help me address my perceived deficiencies because that would be revealing to someone else that I’m an impostor.”
  • Dreaming about leaving. “I think I want to do something different with my career that isn’t available to me here. I do have goals, but I don’t want to talk about them with you for fear of repercussions.”
  • In the zone. “I’m happy with where I am right now. I do not want to get promoted. I just want to come in, successfully do my job, and get paid fairly for that.”
  • No role model. “I have no idea how to do this because I’ve never seen anyone do it well. I’ve not really tried to do it myself.”
  • No point. “This is just HR bullshit. No one pays attention to my goals. I’m going to write them down today and then no one will look at them again until my next performance review.”

Once you understand the root of what makes writing goals feel difficult, you can use that to help craft the type of goals to set. Here are some strategies to unlock the goal-setting conundrum for the reasons I outlined above:

  • Analysis paralysis: You could make finding the “right” focus your goal. To do this, choose one of your potential goals and work on it for a set period of time, up to a month. If you really can’t choose one yourself, ask a friend or colleague to help, or even pick one randomly. At the end of the month, evaluate your progress, how you’re feeling about it, and what impact it has made. If it’s particularly impactful and you’re feeling great about it, you’ve got your goal. If not, you can choose another goal to try for a time boxed period.
  • Future hazy, try again later: You could make figuring out what you want to do your goal. Outline a handful of options for what your future might hold. Don’t be afraid to dream big! From there, you could have informational interviews with people who have followed that path to leverage what they learned along the way. Or you could create a payout matrix to help you think through which path you might want to take. You could create a set of experiments to help you decide what you want your future to hold.
  • Too much happening right now: Depending on why you have too much going on, you could set a goal to reduce the number of things on your plate. What can you offload so that you’re not so overburdened? If you simply can’t offload things, you could instead set a goal to reflect on your situation and what you’ve learned from it. These types of retrospectives can help you and those around you avoid getting into situations like this, better handle those inevitable times when it feels like everything is going wrong at once, or even simply recognize that this happens and sometimes all you can do is keep on keeping on.
  • Impostor syndrome: Setting goals to help overcome impostor syndrome requires vulnerability and support. You have to be vulnerable in admitting that you feel this way, and you have to have support from a good leader who will help you move past it. If you aren’t sure if you’ve got a good leader or you’re not ready to be vulnerable, one way to sidestep this is to leverage your career ladder. Look at the competencies for the next level. They’re probably the same competencies as your current level, but they have broader scope and impact. You can frame your goals in terms of growing to that next level. You could also set a goal about getting in-depth 360-degree feedback from those around you to help you better understand what you’re great at and what you’re not, if that’s not already part of your performance review. That might help you combat your impostor syndrome, or at least help you decide where to focus your energy.
  • Dreaming about leaving: This is another one that requires vulnerability and support. If you’re ready to be open that you’re thinking about doing something else, you can set goals to make that decision. If you’re certain that you want to move on, you can set goals that help you and your organization be ready to move on, such as ensuring that you’ve wrapped up a key project and fully documented all of that great knowledge that only lives in your head. If you’re still exploring options, you can follow the strategies above for “future hazy, try again later”.
  • In the zone: You could make your goals about cementing your place as a solid contributor. Potential goals include improving documentation, improving processes, or mentoring.
  • No role model: Ask others to share their goals with you. Personally, I like sharing my goals with my team so that they can see what I’m working on.
  • No point: You can choose to treat this exercise as only an HR exercise, or you can choose to treat this exercise as something that you do for yourself. Setting goals is about your professional growth. You have to reframe the exercise for yourself and not let poor implementations of goal-setting get in your way.

As you’re framing your goals, you can use strategies such as SMART goals to help you create meaningful goals that you can make progress on. After you’ve done that hard work, the next step is to create an accountability structure to help you make progress. I like to set up monthly check-ins on my professional goals with someone such as a manager, a coach, or a colleague. That external accountability helps remind me to invest time in my goals, and reflect on what I’ve learned as I’ve worked on them.

climbing the leadership ladder: from manager to director to VP

Recently, I’ve been asked several times what I’ve found to be the difference of being a manager, a director, and a VP. Each of those roles is an interesting one with its own challenges. My thinking on this is heavily influenced by this blog post from Peter Merholz. In his post, he introduces what I think of as the three distinct modes of management: managing down, managing to the sides, and managing up.

Managing down is managing those who report to you, or through you if you’re managing managers or directors. Managing to the sides is working with your peers to communicate information, resolve issues, and make decisions. Managing up is the skill of giving your manager, whether they’re a C-level or a senior manager, the tools and information that they need to help you, your team, and your company be successful.

As a first-line manager, where you’re only managing individual contributors (ICs), almost all of your time is about enabling them to be happy and productive. About 60% of your time is directly managing them: keeping them on track, giving feedback, coaching them, making sure they’re working well together, etc. Another 30% of your time is managing to the sides: ensuring that you’re aligned with your peer managers, resolving conflicts, communicating status information, and removing roadblocks. The remaining 10% of your time is managing up: working with your boss to manage priorities, identifying additional resource needs, communicating status, managing the budget, asking them to remove roadblocks, and setting the strategy within your area of focus.

As a second-line manager (for simplicity, I’m going to call this “director”), where you’re only managing managers, your focus shifts. You’re no longer the one directly responsible for enabling a team of productive and happy ICs. That’s the job of the first-line managers who report to you. Now your role is to ensure that the teams who report to you are happy, productive, and working on the right things. For a director, I’d estimate that 40% of your time is managing down to the team: ensuring that your managers are being effective in their roles, coaching your managers in how to be effective coaches and leaders, communicating needed information, resolving issues, setting direction for your team, setting your team’s culture, and removing roadblocks within and for your teams. As a director, managing to your peers is more important than it was as a manager. I estimate that managing to the sides is about 40% of your job. This is ensuring that you and your cross-functional peers are aligned on strategy and prioritization, that you’ve got the right folks working on the right problems across your teams, and that you are removing roadblocks for your teams and for your peers’ teams. The last 20% of your time is managing up: working with leadership to set strategy, communicating needed information, advocating for your teams, identifying roadblocks that need leadership intervention, and so on.

As a third-line manager (for simplicity, I’m going to call this “VP”), where you’re only managing directors, your focus shifts again. Now your directors are the ones responsible for having their teams be happy, productive, and working on the right things. You are accountable for all of that, plus be part of the team responsible for setting corporate strategy, and delivering on the commitments that you are making on behalf of your team. This means that much less of your time is managing down, maybe 20% of it. Managing down involves is communicating strategy, coaching your directors, resolving conflicts within your organization and between your organization and others, setting your organizational culture as part of your overall company’s culture, and ensuring that your directors are aligned amongst themselves. Managing to the sides is still about 50% of your job. Now that it’s at another level higher, it is even more cross-functional. Now you’re setting strategy across the entire company, identifying opportunities for your company, setting policies, removing roadblocks across your org and for your partner orgs, and communicating needed information across the company. The last 30% of your time is managing up: working with the senior executive team on setting strategy, communicating, making decisions, representing the company, and so on.

Looking back at Peter’s original post, the percentages that he lists don’t match my experience. I think he’s underestimated the amount of time needed at each level to manage up and to the sides, especially at the lower levels. While Peter frames his thoughts in terms of design orgs, I’ve found in my conversations with other leaders as well as my own experience in managing engineers and product folks that it’s held generally true cross-functionally.

If the things that you love are communicating, unblocking, and coaching, you must do more of that at higher levels. The shift that you’re making at each level is that you’re more abstracted away from your core discipline, and that you’re seeing and making decisions on a much broader swath of the company and the business. You are responsible for making a lot more decisions, often with less information than you  would like. I’ve found it to be a lot of fun, and a lot of responsibility.

making research more collaborative

Recently, I was talking to a new researcher who is struggling because they feel siloed off from the rest of their organization. “Is this really what research is like?” they asked me, after describing a research process conducted almost exclusively by themselves.

One of the things that I like the most about research is how collaborative it is. I shared several ideas for making research more collaborative, including the following:

  1. Make the planning process collaborative by involving others (other researchers, designers, PMs, anyone who is interested!) in the creation of your test plan. 
  2. Make the research phase collaborative by inviting others to your sessions, or asking others to take notes for you.
  3. In the days of working in-office, I used to bake cookies for my research days to incentive people to come and watch the sessions. While they were watching, I gave them a short questionnaire to fill out while watching the session. It was lightweight enough that it didn’t feel like the observers were being imposed on. Questions on it were:
    • What stood out to you the most?
    • What worked well?
    • What didn’t?
  4. Make the analysis phase collaborative through brainstorming sessions. Take the insights that you gathered during the session and run a workshop with colleagues where you identify themes and potential recommendations to address the issues identified.
  5. Make the outcomes phase more collaborative by scheduling watch parties, where you show some videos from your sessions. This could be one particular participant who had a lot of insight to share, or it could be a collection of clips that show a theme.
  6. If the designers who you work with have some kind of critique session set up, start attending them and sharing your research materials for critique there.
  7. If you have enough fellow researchers, create a critique session where you give and get feedback on your research plans, performance while interviewing participants, or final reports.

leadership lessons from Mike Kruzeniski

Tomorrow is the one-year anniversary of the death of Mike Kruzeniski. He’s been on my mind a lot in the past couple of months, not only because of this anniversary.

I got to know Mike when he became my boss. He was hired as the very first VP of Design and Research at Included Health. I was a bit nervous during my first few meetings with him, balancing making him feel welcome in his mid-pandemic start, showing the value of my research team, and helping him get acclimated to the new company. He quickly won me and the rest of our design and research teams over.

Mike cared deeply about the craft of design. He wanted design to be beautiful and powerful. He bonded quickly with the designers and encouraged them to uplevel their skills. He gave them space to be creative and to push the boundaries. He didn’t hesitate to roll up his sleeves and get into the details. The design team flourished under him.

I have to admit that Mike’s care for the craft of design gave me pause when he started. I’ve worked for multiple design leaders who pushed designers to greater heights of creativity, and in doing so relegated user research to doing nothing more than validation research to prove how creative the design team was. Not Mike: his support for user research was boundless. He knew when and how to use research. He understood the value of generative research. He knew how to talk about its value to the executive team. He never talked about the design team, but rather the design and research team. My research team loved him just as much as the design team did.

One of Mike’s top strengths as a leader was that he believed in his team. He didn’t second-guess. He asked coaching questions if he thought that something hadn’t been considered. He always made it clear that not only did he trust his team, but he was also all-in on their success. I was the beneficiary of the opportunities that he created for me to grow my skills. At first, I didn’t even realize that it’s what was happening, but quickly came to see the pattern in as I observed him do it for me and for many others across the design and research team.

In addition to his innate belief in his team, Mike was vocal in sharing that belief. If I ever admitted that I was anything less than completely confident that I was going to be successful in something, he was there to cheer and to support. One of Mike’s friends called him the antidote to impostor syndrome, a description that I must agree with. He gave ongoing feedback and advice while reminding me that he believed in me and had no doubts that I could do it.

Although I didn’t get nearly as much time with Mike as I was hoping to, I still learned so much from him. His leadership style has informed a lot of who I am as a leader today. When I was first offered the promotion to VP of Experience Design at Babylon Health a couple of months ago, I immediately wished that I could call him and get his thoughts on making that transition.

I wish I could call him and thank him for everything. I’ll have to try to do him proud instead.