Still, in a company with design approvals and a history of handing down information architecture to developers it’s tempting (I’m tempted) to ward off complications by cooking up visuals that are irrelevant, obvious or subject to change, “pushing pixels that won’t even exist later.”<\/a> <\/p>\n At first, you create formalities around your agile process to protect your team but with success you get opportunities to teach by doing — to demonstrate work is unnecessary by not doing it<\/em>. <\/p>\n All this hit me today like it had never occurred to me before even though I’d read, thought and said some variation of it so many times I should have put music to it by now.<\/p>\n We’ve earned some trust. As my team starts building our first web products for our company, I think it’s time to end our infatuation with 800×600 jpegs.<\/p>\n","protected":false},"excerpt":{"rendered":" My company loves Photoshop comps. Way too much. I know this and yet, to some degree, I’ve enabled it. It’s not original of me to say that static mockups are misleading and often unnecessary. 37 Signals fairly shouts it. It’s … Continue reading ![Whiteboard Sketch](\"http:\/\/judykat.com\/ken-judy\/wp-content\/uploads\/2007\/07\/whiteboarddrawing.jpg\")
My team walks this talk. We co-locate our designer<\/a> to pair with our developers. We present product ideas using hand drawn sketches<\/a> and narratives. <\/p>\n