More on this book
Community
Kindle Notes & Highlights
Another implication is that there should be only one design organization to undergird the entire customer journey. This runs contrary to a common practice, where companies often have two teams — a product or UX design team and a marketing design team. This is the legacy of 20th-century mass manufacturing thinking, where the way a product is designed and developed is divorced from how the product is sold and talked about. In a services world, this distinction no longer holds. “Marketing” and “product” experiences are simply milestones on the same customer journey. Also, whereas traditional
...more
recognize when something is “ready,” because with software, you’re never really done.[
Design may be seen only as aesthetics and styling, or as one former client referred to it, “SUAC: Shut Up and Color.”
users (Growth and Reviews). These product teams report up through a VP of Product Management, but otherwise don’t have much structure overlaid. An embedded model would place designers within each product team. While the Centralized Partnership could mimic that, with design teams organized by product, what’s more appropriate is an independent structure overlaid on this product organization, supporting distinct buyer and seller experiences (Figure 4-4).
“What were her strengths as a team lead? Her weaknesses?” “How did she help you in your work?” “How was she in working with engineers and product managers?” “Were I to hire this person, what would I need to do as her manager to help her be successful?”