How do you work with UX Design?

In my previous company, SpiralEdge, we did not have a dedicated UI/UX team. I had to learn how to wireframe UI’s all on my own. For those starting off, I recommend a tool such as Balsamiq. They say imitation is the sincerest form of flattery so my first foray into creating wireframes was to borrow elements from my favorite sites and apps. A good rule of thumb is Steve Jobs “3-Click Rule.” In other words, it should never take your users more than 3 clicks to navigate where they want. This rule has been challenged as of late (see UXMyths), but for the most part, you want to keep your clicks to a minimum (even if it isn’t 3).

How do you work with Tech/Engineering?

For engineering its important to have enough basic technical knowledge on our user flows and logic should work. You need not define requirements down to the code-level, nor should you want to. Empower the engineering team to choose their preferred way of implementing the code that delivers the flow you outline in your requirements. Collaboration is key, If an engineer challenges you, welcome that challenge. They may have reduced the amount of engineering effort or user’s path to resistance that you didn’t know existed!

How do you work with Business?

The bulk of your project requests will come from this part of the company. They serve as your primary eyes and ears on what’s happening out in the field with your clients if you’re B2B and consumers if you’re B2C. However, there are often more product requests than there is bandwidth. The key here is prioritization. For each product request, take a step back to review if it is necessary for the product, or if there is an alternative option available. Ask yourself, does this feature or enhancement really solve the problem? From there, if it does seem like a viable solution, the work involved will need to be estimated. Writing product requirements, kickoff meetings, design, engineering at QA all need to be factored into the estimates. In addition, if one project is prioritized over another, any timelines that suffer do to reduced bandwidth need to be communicated. It’s a balancing game of level of effort (LOE), return on investment (ROI)

In the end, remember in the world of product management. You own the product, but no one reports to you. In order to be successful, you need to ensure those contributing to your product are invested.

Works Cited: Gonzalez de Villaumbrosia, Carlos and Anon, Josh. The Product Book: How to Become a Great Product Manager: Product School, 2017. Amazon Books 3 Jan. 2017