Okay so. I keep seeing this happen. Your product has two users. One screen. Both at once. A customer. A mechanic. You fix it for one. The other side breaks a little. I ran into this myself. On a mechanic-booking marketplace. Customers don't know car terms. They can't describe the problem right. Mechanics need real detail though. Or the quote is a guess. So you're stuck in the middle. Design for the customer - mechanics get vague, useless requests. Design for the mechanic - customers feel interrogated before booking. Your first instinct is simplify. Shorten the form. Make it feel easier. But shorter isn't the same as clear. A shorter form that still confuses the mechanic? Didn't fix anything. Just moved the confusion downstream. Here's what actually works. It's not about length. It's about order. What each side sees. And when. So neither one is left guessing. If you're building anything two-sided - a marketplace, a platform, even a simple request flow - this is the part worth slowing down for. Before you touch a single screen. So tell me - on your product, right now - whose confusion are you solving first? And whose are you quietly leaving for later?