Remove Definition Remove Naming Remove Systems Review Remove Weak Development Team
article thumbnail

Build Team Resilience: Shorten Feedback Loops (Part 2)

Johanna Rothman

This series is about helping a team create a less brittle environment—more resilience. Brief description of the problem at a recent client: Person A checked in code that broke an “unrelated” part of the system. Yes, I changed the names of the functionality because the names don't matter.).

article thumbnail

How To Improve Designer-Developer Collaboration as an External UX Team

UX Studio: Product Management

At UX Studio , while we develop our products, uxfol.io and copyfol.io , we are mainly focused on agency work, meaning that we cooperate with several clients as external teams. This post was written from the perspective of designers, mainly intended for external teams and entrepreneurs. Five challenges and solutions.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Product Bugs: A Comprehensive Guide?—?Part 1

The Product Coalition

Some people want to believe that they won’t happen or don’t want to talk about them so that they don’t risk being seen as bad at their job. I’ve never seen a roadmap naming the bugs a team wants to introduce?—?but For our purposes, we’re going to use the same definition for product bugs. of the gross domestic product.”

article thumbnail

50 UX UI portfolio intros you can “borrow” from Google, Apple, Facebook & Uber hires

UX Planet

Firstly, this is definitely what a recruiter is going to read and evaluate first as a potential indicator to whether they should hire you. A bad first impression could ultimately hurt your chances of landing a dream job. People see selling as a bad word but it ultimately makes life easier if you know how to do it.

UX 85
article thumbnail

The UX of Data

Amplitude

People in non-technical roles rely on data every day to make decisions, develop ideas or measure success. When tools and systems are not created with them in mind, they lose trust and understanding. You may not understand someone else’s definition or report. He’s been conditioned to not bother the data team.

article thumbnail

Technical Women Are Software Managers

Johanna Rothman

One of my reviewers for the Modern Management Made Easy books asked a fascinating question: I've never seen this many women in management or in senior leadership positions. Too many of these educated people had no idea how to work as a collaborative team. The idea of a code review or a design review? Consider the System.

article thumbnail

The Product Interview?—?A Technical Exercise

The Product Coalition

My take on it: while I love ex-developer PMs, and find that their teams often execute better, this is by no means a requirement. However, if a non-techy PM meets a non-businessy team lead, things can go sideways pretty quickly. while the user name does have a unique id, the team and content do not.