Occasionally I'm asked to provide an opinion about a topic that people think I should have some authority to comment on for some reason. That topic, as you might guess, is wireframing.
I enjoy pointing people towards good resources, or helping them with a problem using a tool that I'm familiar with. I also love to give my own design resources to peers, or to teach techniques that I think will help people perfect their craft. In the end, I benefit from that exchange the most.
When asked to comment on slanted opinions that throw a stake in the ground and tend to confuse and divide the community, I abstain. Navel gazing and defining the damned thing became an uninteresting use of time to me long ago. It took some time immersed in those conversations to know that I have nothing to contribute. I'd rather be making stuff than talking about it. I just say call yourself whatever you like, and do whatever works.
Interface design tools are as good as you make them. When I started out, I had to use Visio to communicate UI specs. It wasn't awesome, but I made it work. Later I found Omnigraffle. It was not designed specifically to enable interface designers, but we made it awesome. We learned how to use it to make our documents communicate design ideas.
We are the ones who determine what's useful for us after immersion in tools. We've debated what we want in the ultimate IA tool, we've found parallels in other industries and fields of practice and made them our own. We've experimented with forward-looking low-fidelity prototyping projects like Denim, and pondered what the right suite of tools are for our work. Some of us built them and shared our work. Some of us are still building them.
Over years of working and watching others work, I've noticed that some attributes are common among the people whose work I admire. The people who are the most effective seem to continue to study their practice, and perfect their craft. After long hours of use, they find the way to flow within any app at their disposal, and become as fast and effective as they can using it. The key is what they do with the app once they've become expert at their craft, expert in finding the right design, expert in communicating, and expert in refining. There's some kind of maker/doer tenacity I see in people, and it doesn't have to do with any one tool.
There are no good or bad tools for finding the right design. Paper prototypes are your thing? Awesome. If you want to sketch and go right to building in HTML? Go for it! I've done it. You want to craft gray box schematics in OmniGraffle, Photoshop, or Mockups? Godspeed you wireframer. Maybe I can help you with that. You want to use a tool that generates interactive prototypes? Have a nice day. 🙂
All the side-taking is useless to me. If you've ever interviewed people for an IA or IXD position, you know that beautiful documents and prototypes are meaningless if in the end they don't demonstrate good problem solving and good design decision making. I don't care what people use. They can use finger puppets and crayons if they help them.
I say use whatever makes sense or is at your disposal. Your tools are only as effective as you are at using them to accomplish goals. But don't let anyone tell you that what you choose is wrong or inappropriate. Find the right design and keep winning.