Observation created over 4 years agoJoesph was given a big problem. Search on the learn page is slow. The big problem is determining what lessons a user has access to. The majority of the problem has to do with lessons in paths. This was not a part of the application that he had a lot of deep knowledge in. He took a lot of time to create test data (paths in paths in paths with lessons all over the place) and has worked to really understand how all of the parts work together. In fact, I would say know that he really groks it in a way that I do not. I offered him an initial design on how we should solve the problem. After working through all the details, he saw an even better solution that take the last couple steps in the journey to search nirvana. In the midst of all of this, he has done an incredible job communicating the changes with the benefits that they will bring.
Observation created over 5 years agoFeaturing:Ethan M.Joseph A.Joshua A.Waseem D.We ask clarifying questionsWe get agreementsWe inspire others to do better workCommunityDesign CollaborationBack-end engineerFront-end engineerDiscovery engineerEpic shaperStory shaperI am grateful for how these 4 have been communicating on this project. This is a complex project for a variety of reasons. We are splitting up the frontend and the backend. Linking elements in our app is a difficult endeavor. The way these four have communicated to one another and to me has been such a joy. Whether it be Waseem posting killer updates in the channel, Joshua and Joseph presenting their findings on technical deep dives, or Ethan walking me through expectations on epic breakdown, everyone has chipped in to really get this off the ground.
I have been inspired to bring the level of clarity I have found here in other aspects of my job.