{"id":373,"date":"2024-04-26T11:03:13","date_gmt":"2024-04-26T10:03:13","guid":{"rendered":"http:\/\/localhost:8082\/?p=373"},"modified":"2024-04-26T11:19:59","modified_gmt":"2024-04-26T10:19:59","slug":"product-vs-delivery","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2024\/04\/26\/product-vs-delivery\/","title":{"rendered":"Product vs Delivery"},"content":{"rendered":"\n
Have you ever been asked to write requirements for a poorly defined, sometimes non-existent product?<\/p>\n\n\n\n
Worst still, have you ever been expected to produce wireframes and UI designs on behalf of an absent or unappointed product owner?<\/p>\n\n\n\n
Unfortunately, it\u2019s an all too familiar situation.<\/p>\n\n\n\n
These days, I walk clients through a simple cheat sheet that visually explains the difference between product design and software delivery. The confusion is usually quickly cleared up and responsibilities allocated.<\/p>\n\n\n\n
Failing that, you at least know where problems will likely happen and how to spend your time ie. making the case for a product owner and product design function.<\/p>\n\n\n\n