I learned a lot from that. Thanks. The notes on the specific testing and implementation was great, but also the general tone of the piece. It can be hard to wr

I learned a lot from that. Thanks. The notes on the specific testing and implementation was great, but also the general tone of the piece. It can be hard to write about marketing to an engineering audience while honoring an engineering-driven culture. For instance - > FogBugz exists to help software developers write great software, but it also exists to pay the rent. This means that we have to actually consummate transactions on our website. This was previously delegated to the curiously named “Details” page. It had been designed primarily to explain to customers the difference between FBOD and the downloadable version of FogBugz. Sadly, this ended up being quite confusing. Covers why marketing is needed in an extremely straightforward way (...it also exists to pay the rent). Then, it logically follows the page that converts needs to be easily accessible. And then, the notes here and elsewhere that non-technical people are often hitting these pages and getting lost trying to decide on the tradeoffs. Great piece. Learned about the specific measures you took, but also a lot of meta-learning about how to present things well. Extremely straightforward, logical, acknowledging and honoring the engineer culture, while also noting that marketing needs to be part of the process to pay the bills and get the product in users' hands.