I am not a trained coach or teacher but our work involves a lot of education, building the right conversations with the right people for how we should design and ship products for the real goals. So often, it is about identifying the goals, communication, clarity in how we work, and defining some standards or guidelines in the teams for how we all should work together for the common goal.
When we guide or train someone, we want the audience to ask questions.
How coaching helps
In my opinion, the real coaching for the working professionals is very little about the product, or design, or content, or architecture. They can learn the tools or coding practices by the vendors or on tonnes on Youtube videos. Coaching is a lot about self-discovery.
For example, if we have a workshop on how product content strategy helps UX writers, then the participants should can have two different takeaways—A or B.
- A—Yes, I need to see how the content in the shopping cart aligns with the brand voice and tone. Now, I understand how product content strategists make it possible. I can write the shopping cart and checkout step content more clearly and accurately now.
- B—Yes, I need to reach out to the product marketers for what they say about the guest login checkout. Do they follow the style guide or the design system for the brand voice? Are they communicating in the way our product guides them in the checkout? I need to ask them and now I am more confident to frame my questions, and the timing of raising these questions.
B is more likely to apply their learnings in their work.
Shreyas Doshi ran a Twitter poll for a possible coaching program.
If I were to (purely hypothetically) offer a multi-day advanced workshop on a product topic, what topic would be most interesting to you personally?
— Shreyas Doshi (@shreyas) March 11, 2022
Optionally, reply below with your ideas on format (duration, frequency, sync/async, prefer group activities or not, etc.) 🙏🏾
Later, Emily Patterson tweeted about the Product Sense part in Shreyas’ tweet.
I have been thinking a lot about Shreyas's poll the other day asking if people would be interested in a course, and one of the topics was "product sense". Like, can that even be taught? And how?
— Emily Patterson (@epatt6) March 13, 2022
(I like Shreyas and this is not a criticism of him, just been on my brain a bit)
The discussion shows that the audience and the community in general agree that training someone in product means training on many soft skills and inter-personal skills or technology-adjacent skills rather than teaching tech itself.
The goal of any such course is not about how we can design or develop digital products. Why we work in certain ways in general or in specific situations, how we make decisions with others, what drives us, what builds us—this is the core objective of coaching. The takeaways are clarity, awareness, and it should leave us with right questions and leave us prepared to find the answers in our work.
Finding questions in the conferences
I always traveled for the tech conferences to find how people work, how they plan their work, and how the talks build conversations. My takeaways from the conference have always been finding the questions and framing those questions, and not directly seeking the answers to my questions.
The goal of a tech conference is not to answer the questions thst audience might have. The goal is to help them find and craft the right questions and let them find the answers in their real work. This is what I was always doing at my own UX conference, Outcome.
— Vinish Garg 🎗 (@vingar) January 27, 2022
Finding questions in team meetings
One of the most important skill that I build in my team, is to ask lot of questions.
1. Asking the right questions at the right time and making my team learn to ask the right questions at the right time
— Vinish Garg 🎗 (@vingar) March 15, 2021
2. Be really unforgiving for the product standards that we define inclusively; it might sound harsh but products dont scale by trial and error
The timings as the function of their work – whether to ask right questions at the right time, with one eye on present (deliverables, quick wins) and another eye on the future (what if, bigger goals).
— Vinish Garg 🎗 (@vingar) July 24, 2020
Many products die because of lack of conversations in the product team. Specs and Slack are not conversations. The leaders don't discuss it enough and so they have nothing to walk the talk. The sales pitch is not the talk. Why, how, why with product teams are the talk. https://t.co/BhSGm430YC
— Vinish Garg 🎗 (@vingar) December 13, 2021
Questions in coaching and learning
When I was talking the content design classes for the FH-JOHAEN university students earlier this year, I made sure that I was preparing the students to ask me lot of questions. Sometimes, I would leave a conversation to see if they smell an opportunity to ask something, and sometimes they did. Our discussions were a lot about framing the questions, why it is important to ask questions, and why to keep our minds open for the impact of our work beyond the interface.
We learn by asking questions, and then by trying to find the answers in our work or workflow.
Now it is your chance to ask me any questions. I am on Twitter.
—
I plan to discuss this topic in my advanced course in product content strategy, content design, and UX Writing. See the course details for how we can find and add more meaning to our work.