Give More. Get More.

As SDL Tridion MVP Selection Panel chair, Nuno Linhares has called others in the Tridion community to action and has recently blogged about the the art of knowledge sharing . He offers some reasons he's had to not share (knowledge = organizational value, faster to solve than teach, and fear others will steal) and compelling reasons to share (recognition, ability to scale, job/career mobility). I've seen both sides and share my background with sharing below. I'd like to add that sharing can be scary, especially when you're not sure of how a message will be received or confident in what you know.

I've enjoyed everything from mentor roles to being seen as "the guy who does too much" to being called arrogant and immature, so take the following from the perspective that I've done okay so far, I believe in the value of sharing in your chosen interests and industry, and I have a lot more to learn and grow.

I've found career and personal satisfaction from creatively contributing in authentic ways (yes, I'm a fan of Seth Godin's Linchpin). In terms of knowledge transfer and sharing, I've been "rewarded" with bigger and better projects the more I gave old projects away.

As a Web-development-intern-turned-researcher, I've reported on everything from software development tools to industry news to competitive assessments. From screenreader software that read websites to blind users to enterprise-level content/workforce management systems, I received bigger and more interesting prompts the more I put into the research.

Gave away Roles. Got new Roles.

Also known as "I killed my previous job" through sharing or intentionally making myself obsolete.

I helped train other interns, explaining everything from laptop setup to who's the right person to ask what question. I eventually helped the development team select their Web Content Management System (WCMS). Fascinated by the chosen solution (Tridion R5.3) and eager to learn, I effectively killed my previous job of manual Web content updates, HTML edits, and SQL scripts; I still apply these skills but in somewhat more interesting situations.

I got a new role as a business analyst (BA) to support the WCMS and continued to help end users and developers. I learned from, and then contributed on, the Tridion forums (enough to win a nifty, sharp, and deadly-looking SDL MVP award).

I documented everything from user guides to system diagrams to requirements and encouraged others to update and share their own write-ups. I offered expertise when requested (and sometimes when it wasn't!). This coincided with another shift in responsibilities towards vendor/partner implementations and a promotion to a (cross-functional or "weak matrix"... just so you understand I wasn't directly leading teams) project manager (PM).

As a PM, I was able to leverage vendor evaluation skills learned from WCM in a WFM (workforce management) assessment and eventual implementation. I've enjoyed the role, but missed the collaboration with the solution and community that helped shape my career.

Sharing your way into New Ventures

In terms of that intersection of skill, will, and motivation I've found a sweet spot between these various "jack-of-all-trade" roles of BA, PM, and resident Tridion subject matter expert; I've applied for, and accepted a new position as a functional consultant with SDL Web Content Management Services (professional services) (My site disclaimer still applies; this blog does not reflect the views of my current/past/future employer unless otherwise stated. I've accepted an offer but don't start for a few days.).

I owe so much to my previous roles and will always have love for American Specialty Health, but I'm looking forward to learning, growing, and sharing with my new team and helping other SDL clients.

Semi-final, random thoughts on sharing

• Though I've played various roles, there is nothing wrong with becoming an expert in any given role. I'm not advocating leaving your existing job and the intention shouldn't be to "jump ship" as quickly as possible, but to transform our roles to include More Great Work (Michael Bungay Stainer).
• Think big! There are lots of after-school activities where a single coach or instructor will attempt to help an elementary school. But what about a program that teaches teachers instead of a single classroom? How can we scale from classroom to district? From one company to several?
• I've helped a development team, an IT department, a medium-sized corporation, and a community of Web content management customers. My long-term knowledge sharing goals include either contributing to an industry or combining current and past interests to offer something new.
• I didn't plan or think I'd be qualified to join SDL. I believe knowledge sharing works better when you're authentic and genuine ("white hat" sharing preferred--I don't believe my specific "path" and approach would work if I only shared for personal gain). Daniel Pink's Drive confirms that rewards and incentives are more effective as "now that (you've done something good)" surprises rather than "if (you do this) then (you'll get rewarded)." I agree with Nuno--it only took a kind word or encouraging email to feel appreciated for sharing.
• If you give a man a fish he eats for a day. If you post fishing video on YouTube you can reach thousands of viewers.

We share, teach, or advocate because we love a product, solution, or idea. If we're lucky and find that right intersection of an appreciative audience and fascinating topic, we can feel like the bee girl at the end of Blind Melon's No Rain. Well, at least that's the closest popular-media-metaphor for how I feel when collaborating on interesting projects or talking Tridion with other consultants.

Well, that's what knowledge sharing, teaching, and contribution has meant, and continues to mean to me. I'd love to hear your successes and challenges with your own attempts and sharing, advocating, and being an ambassador for whatever fascinates you.