TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
This is the best place I've ever worked as far as seeking and
respecting input from everyone on the team. I frequently do
html mock-ups that are living documents from which the
interface design evolves. One of the bosses told me that he was
happy to have me spending my time on the interface rather than
the help system, because it was his goal that the interface
become so intuitive that the help system was just icing on the
If I see an interface inconsistency or simply something that's
hard to document, the developers listen. At the same time, I
appreciate the input/feedback I receive for documentation. The
thing that makes everyone receptive to comments from a wide
range of contributors here is a common interest in making the
product better for our users.
You mention that it's your goal to "become in charge of the
design of the interface AND also be responsible for the
documentation." FWIW, projecting a desire to be in charge could
be off-putting to those currently doing the interface design.
Understandably, you want to put your training to use, but you
can do that without being in charge. By focusing on the good of
the project/product over your personal goal, you're less likely
to meet resistance. And, once you prove the value of your
contributions, you'll be in a better position to meet your goal
of being in charge someday.