How to Publish Professional & Tactful Teardowns

Published September 26, 2016 by Jane Portman

Today I’m answering a question from Anna Sabramowicz, an e-learning strategist. Anna would like to publish teardowns within her knowledge domain, and is asking for advice:

“Teardowns are obviously an excellent way to show domain expertise and market yourself. My question is, should I simply find things that are public on the web and do a teardown? Or should I be more formal and notify the owner, or ask for permission? Any lessons learned or things I should watch out for?”

Thank you for the great question, Anna! I’ve never encountered any problems with the teardowns. However, I’ve chosen to follow certain principles (voluntarily):

Also, practice makes perfect — do your best to publish tearowns regularly. This will help you develop your own voice, format, and professional reputation.

Ready to ask your own question?

That’s great! Submit your question using this form (it should only take a couple minutes). I’ll do my best to answer as many as I can.

The 1-Hour UI Audit: Get Your Free Course

With this free email course you’ll conduct a simple do-it-yourself audit of your web app: eliminate the obvious design flaws, gain control of your features, and start building the UI that customers really want.