A User Guide to Working with Joshua Litchfield

Introduction

Working in technology and being an American working in the city of Boston, I communicate every day with colleagues and people from different cultures, backgrounds, and life experiences. My wife, who is from Italy, can have entire conversations with her family using just her hands! Every day at home, I experience the differing views of success, communication, and work-life balance between our two cultures.

I wrote this user guide to give you a better understanding of me, my values, quirks, and growth areas so that we can develop the healthiest relationship possible. I encourage you to do the same and share your user guide with me as well!

How I view success

  • Inclusivity: No matter our birthplace, cultures, religious beliefs, gender, sexual orientation, or skin color, most people all want the same thing. People want to be happy, healthy, safe, and to be accepted by others.
  • Integrity: Caregivers and people receiving care require their healthcare professionals to have strong moral and ethical principles. The designer and the experiences he creates require the same rigidity and adherence to these principles.
  • Continuous learning: Product Design is a relatively new craft with a deep history with roots in graphic design, fine arts, and other fields. I respect others with a continuous learning mindset in their chosen craft because that is what it takes to succeed.
  • Continuous improvement: One of the goals of constant learning is improving your expertise and applying it to your chosen craft. I also appreciate designers who strive to improve their products through user feedback, data, and other sources. I also respect product designers who are always tinkering with the product experience to enhance their app.
  • High standards: I place a high standard on myself and the products I buy. I thoroughly enjoy the “little big details” or micro-interactions that provide magical moments for users. These little details separate good products from great products. Do what is right, even if it is hard.
  • Outcomes, not features: People “hire” applications to help them do a job faster and more efficiently. As a product designer working in healthcare, I devise experiences where patient outcomes matter. I respect product stakeholders focused on improving outcomes rather than adding useless or “nifty” features that hinder results.

How I communicate

  • My internal train of thought is continually running in the background while listening or speaking with others. It is always looking for a connection to anything relevant to the conversation at hand. This “background job“ occurs both when I am speaking or listening to others.
  • When speaking, I sometimes find it hard to “stay on track” with my message because I've thought of something pertinent to the conversation which isn't in the document I'm presenting.
  • When listening, I sometimes impulsively interrupt you because I am so excited about what I thought of that I feel the need to do so. I am working on writing it down or keeping it in short-term memory to share when you're done speaking.
  • I believe my verbal communication style is casual and friendly, but the written word is more formal and grammatically correct.
  • I use obscenities when I am passionate or upset about a topic. It is not often, and I do this for effect.
  • I have a focus block every day from 12 PM – 3 PM. I prefer not to have sync meetings scheduled over that time, but I am OK with meetings and conversations that move projects forward.
  • Microsoft Teams or a similar solution is the best place to get my attention for quick inquiries. Still, I prefer video or in-person conversations for prolonged or complicated subjects.
  • I manage my to-do list in a standalone application. I don't do it in my chat or email client, so I don't have a preference.
  • Outside of office hours, I tend to turn off notifications and don't check email. Family and work/life balance is different in Italian households, which I adhere to those more so than American norms. However, I monitor email and work more when required.

Things I do that may annoy you or be misunderstood

  • For most of my career, I've worked as a solo designer. As a result, I haven't had the luxury of time or access to UX researchers and often “relied on my gut.” In a sense, I've worked a vacuum. As a result, I can sometimes be too defensive when receiving feedback. Sometimes I need a moment to think about it. I am proactively working on improving this.
  • As a designer, I am most often thinking and designing for future states. For some stakeholders, this can be frustrating when trying to solve something in the present.
  • I am very rational, sometimes to a fault. As a result, I sometimes have trouble empathizing with people.

My strengths

  • Healthy relationships: One of the leading contributors to a successful product and company is the people working there. Also, we spend more time with work colleagues than family members, even in the pandemic era. I need to have good, healthy relationships with those around me, whether at the office or home.
  • Honesty and transparency: These two principles allow for better management, the right career choices, and overall trust and security in the relationships we have with each other and the company that employs us. I would rather be open to a candidate and have that person make their own choice rather than deceive them.
  • Ability to see short and long-term vision: When designing new features for the product, I have a good sense of where it might in the long-term then break it out into small, useful chunks.
  • Strategic Partner: The product experience lives at the intersection of the business and user needs. One way too far in either direction won't serve either party well. Balancing those needs is one of the primary goals of the product development process.
  • Creating frameworks: The application footprint of the healthcare professional is extensive and requires several skill sets. Building these complex products and interactions requires systems-thinking frameworks allowing for faster learning and apprehension of the products.

My growth areas

  • Understanding the problem: Relying on my gut has served me well over my career, but interacting with users throughout the product development process is invaluable. I am learning more about jobs-to-be-done, outcomes-driven methods, primary and secondary research, reframing the problem, etc.
  • Application design: I am confident in my knowledge of UI controls and best practices. However, I plan to increase my understanding of systems thinking approaches related to the end-user experience. Therefore I plan to learn more about object-oriented UX, natural-oriented UIs, and task-driven UIs.
  • Expanding domains on knowledge: If I want to be more successful in the vertical I work in, I must continue to learn more about models of care, caseload management, task management, automation, to name a few.
  • Communication: I've identified the need to interact more with stakeholders and users throughout the process. To be successful in that endeavor, I must also improve my communication skills. Therefore I am honing my improving active-listening skills, using less technical jargon, proactively documenting design decisions, storytelling, presentation skills, communicating using the pyramid technique.
  • UX writing: Microcopy, labels, error messages, and other text are perhaps the most challenging part of designing the end-users' experience and is an area I am continually working to improve.

My expectations for my reports

  • Open and honest line of communication: I always welcome feedback and suggestions on anything from the design process, tools, my skills as a manager, or input about the company.
  • High standards: I place very high standards on myself. I expect high standards for you as well. I would instead ask for more time to complete a design task rather than cut corners.
  • Commitment to quality: I respect a high commitment to quality. I also appreciate building the correct thing, not the easy or fast thing, and sticking up for it. As designers, we are the “voice of the user.”

Logistics

  • As designers, we will continuously be chatting, doing design reviews, and working closely together.
  • For 1:1s, we will always go over your questions and concerns first;
    • Next, I will share any news I've received from my managers.
    • We will either go over or set-up more time if we don’t cover everything.
    • Discuss objectives for the coming week.
    • Anything else you recommend we add to the format.

Giving and receiving feedback

  • No matter the context, feedback is typically well-intentioned. It would be naive to assume that all input is all good all the time. 😉
  • When giving feedback, I am coming from a place of knowing that I think I possess. If I don't know, I will tell you that I don't know or send you to someone who can better answer your question.
  • I can sometimes give you unprompted input, but I now realize that may come across as rude or myself acting like a know-it-all. I'm working on asking people first.
  • I always welcome feedback in the spirit of continual improvement. This feedback applies to my design, managerial, communication, and “human” skills.
Last updated on November 2020.