Session 4 Summaries – 25 January 2014

Leveraging LinkedIn

Scribe: R. AYALA

  • LinkedIn Issue maybe too many people asking to be invited Responded to uninvited.
  • How do you leverage
  • Resume
  • Documents you have authored. Profile length does not matter recommendations are important, cooperative 3 job entries
  • 2-3 recommendations very important, makes recruiting happier. Recommendations can be denied or not used.
  • People have too many recommendations. Too many endorsements maybe getting too many. Be overt about getting support from last job, currency insight from peers, a major plus. Need evidence from former coworkers, recommendations.
  • Pay premium: suitcase icon looking suppress you want to be anonymous go into option, profile to none, and to first level.
  • Recruiter look at site giving a talk to use as an advertisement make you much more visible suppress people you viewed, embed key words into your profile basic ‘SEO’ key points.
  • Leveraging
  • Forums – Keep up to date meet new people 2008-2009 layoffs, keep in touch with old friends
  • Research what people are doing evaluation, look at dialogue and links to
  • Job boards – jobs are sometimes 350 for 30 days
  • Proactive recruiting identify key people, go out and find people, getting contract workers two way tool – recruiting people moving around a lot of lateral moving, keep profile up to date.
  • Look up company and look for key people, news tailored to certain customize rolodex, concern about privacy change profile, before contact info. Be careful and keep updated.
  • Recruiters use LinkedIn a lot
  • Profile complete and current
  • Portfolio easy accessed that is not difficult to see.
  • 7,000 – 10,000 a year paid, people don’t want to found privacy is strong on
  • Membership levels can be huge, keep profile current premium attachment stating differ gears part open LinkedIn network “lions” open network people
  • Use key words very important in profile. Populate with key words, need to be sound, make yourself more visible by making recruiter work easier.
  • Big Data, Mobile primary tool for recruiters. They are not capable. Search on Key terms, be very specific, need to stress the key job entries. Don’t recite responsible. Stay projects and skill set.
  • Privacy issues on your profile, make sure you don’t give away too much information.
  • Conceptual reference 3-5 content
  • Index
  • Table of Content
  • Don’t name product or substitute important TM with DISNEY
  • Portfolio: put disclaimer
  • Tech support, Help me
  • Quantity specific actions
  • Writing is needed, looking for quantifiable outcome.
  • We need to stress the desired outcome with these results.
  • Blog posts need to show numbers of visitors.
  • LinkedIn will help you get a new job. Brag about this experience where you helped your company.
  • How did you find a way to develop and show that you have transferable skills to possible jobs.
  • We can stress your attitude in overcoming challenges at previous job.
  • Playing up: On LinkedIn we have continued Education. Can share about workshop @ TC CAMP “I can be proactive”
  • For profit,
  • Be careful with blind calls from people you don’t know. They asking to mine your network. LinkedIn premium for a month.
  • Suitcase visible, in mail
  • Send message to anyone not connected
  • In mails obligated to see
  • Long list of people to use
  • Re-use with list.
  • Must elect to use suitcase
  • Introduction: is a request to see a person
  • Referral: request to be in network
  • Recommendation: from former coworker and can help them clarify with letter.
  • Span: endorsements are not counted for much you are trying to connect to these people.

Content architecture and design

Scribe: tonie

Who has control architectures?

  • Documentation based on implementation/industry
  • S1000D standard (data modules)
  • Existing SharePoint structure
  • Examples = structuring information templates

Way to get a handle organization

Mike Biggers says TOC locks you into structure

Content vs. context / movie example

Google, etc. statistically figure out the content that will make you happy

Getting away from book paradigm is hard

Useful chunks

Publishing – printers with duplexing – compare 3 not the same as books

Distributed model = smaller chunk than a chapter or book

Standards

  • Exchanging info with another entity
  • Existing tools and techniques
  • Accept a standard so you don’t have to define one
  • Outside of unmonitored
  • Wiki– no one is responsible for the content; content junkyard

Document review process

Jac – Review process

Small firm merging to big firm – challenge how the review can happen

Dave Gardner – N+N/30 yrs of TN

  • Different places
  • Cisco systematic plan
  • EDCS
  • Review process is in both level of hierarchy review process.
  • Look into the document. Keep track of changes

KYOCERA – English to Japanese – Translate, submit – Japan

  1. Feedback
  2. Technical
  3. QA Review
  4. Freeze

Susan – Betterway

  • Review process from QA/Engineer
  • REST A PI – Technical
  • Review (Technical Review) was a process

1998 – Cisco had process

  • Information gathering – is easy – Review existing documentation
  • A new person is trained well in cisco review process
  • Editorial Review within team
  • Technical Review is done by Engineering
  • Disagreement was solved by Engineers
  • Have interpersonal skills to finish the review the documents
  • Have informal review process and build rapport
  • Share PDFs on server and it sends a link to PDF
  • Have the rule, how the process
  • Chunk the information the review
  • Page review
  • Online review
  • User feedback was given to author
  • Direct user feedback helps author to analyze and improve writing (technical) Doc Review
  • Interesting
  • Educational Process

DITA vs. Docbook

Scribe: Victor Buccieri

Docbook 2000 elements/DITA 500 elements.

Conversion to Docbook (fm ???) was easier than DITA.

Docbook Constriants ??? Inability to easily change minor elements within ??? (below 5 levels down)

Filtering, text entities and file entities discussed.

Dita solutions include filtering and ???

Bob Staton ??? Bush experts.

  • Topic Based Authoring eliminates the numbering and a steep learning concept for non-XML formats.
  • Mini maps allows you more ??? re-use
  • Discussions also discussed customization and types of style starts you consideration
  • CSS and FO differences discussed at length
  • DocBook is letter used for less ??? and re-use.
  • DITA and ??? are letter ??? you more variations and re-use of content

Common source Database

TC and Agile

  • Definition of Agile: Small iteration cycles/rapid changes + incremental
  • Need to tech writers
  • Need roadmap of what product can do before starting (collaborative with team)
  • So that whole team commits to each “sprint” goal

Keys

Either (1) Everyone pitches in to get doc done by each sprint (if needed)

(2) TC commits to “placeholders” + lags behind a couple sprints

Agile is great for:

  1. Quick changes with developing products that need to change if design doesn’t work
  2. Enables rapid feedback as to what we’re doing is
  3. Small iteration cycles/incrementing
  4. For TC-Doc is no longer an after thought
  5. Fix “the pain” if there is any

Writers and product usability

Scribe: Wendy Shaffer

  • Weaseling in – your entry point
  • Error message, labels, on screen help
  • Be involved in the design process – tech. writers often get involved too late.
  • Usability is about time – an unusable product steals time. (Eric)
  • Build alliances with user experience team.
  • Importance of demonstrating value.
  • Uxmatters.com – articles on showing value viral marketing and social media – a bad product creates bad vibes and good usability creates butt.
  • Metrics
  • User success is the most important metric.
  • Style guide for design
  • Web applications can give you metrics about whether the user completed the task.
  • Example: ecommerce site – did the user complete their purchase.
  • Ten hundred word editor – write text using only the thousand most common words in the English language
  • How to train QE people to do usability testing.
  • Agile – it is very dependent on an effective user advocate being in the room during the demos.

Three principles:

  1. Consistent
  2. Minimal
  3. Familiar

General Assembly in San Francisco teaches weekend classes in usability

Don Norman, “The Design of Everyday Things”