SlideShare a Scribd company logo
1 of 56
What do Technical Support want from Technical
Communicators
Lee Mullin
Premium Support Specialist - Autodesk

© 2011 Autodesk
About Me – Lee Mullin

   Autodesk support for over 7 years




© 2011 Autodesk
About Me – Lee Mullin

   Autodesk support for over 7 years
   Autodesk blogger




© 2011 Autodesk
About Me – Lee Mullin

   Autodesk support for over 7 years
   Autodesk blogger
   Live in Sheffield, UK




© 2011 Autodesk
About Me – Lee Mullin

   Autodesk support for over 7 years
   Autodesk blogger
   Live in Sheffield, UK
   Hobbies
        Walking




© 2011 Autodesk
About Me – Lee Mullin

   Autodesk support for over 7 years
   Autodesk blogger
   Live in Sheffield, UK
   Hobbies
     Walking
     Watching sports




© 2011 Autodesk
About Me – Lee Mullin

   Autodesk support for over 7 years
   Autodesk blogger
   Live in Sheffield, UK
   Hobbies
     Walking
     Watching sports
     Live music




© 2011 Autodesk
Who do we speak to in support?




© 2011 Autodesk
Who do we speak to?

   Calm customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers
   Big customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers
   Big customers
   Small customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers
   Big customers
   Small customers
   Internal customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers
   Big customers
   Small customers
   Internal customers
   External customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers
   Big customers
   Small customers
   Internal customers
   External customers
   Intelligent customers




© 2011 Autodesk
Who do we speak to?

   Calm customers
   Angry customers
   Big customers
   Small customers
   Internal customers
   External customers
   Intelligent customers
   And less intelligent




© 2011 Autodesk
What do customers want?




© 2011 Autodesk
What do customers want?

   Answers
   Fixes
   FAST




© 2011 Autodesk
Why do they want answers?




© 2011 Autodesk
Why do they want answers?

   They can’t find the answer easily




© 2011 Autodesk
Why do they want answers?

   They can’t be bothered looking for an answer




© 2011 Autodesk
Why do they want answers?

The answer isn’t available




© 2011 Autodesk
How do we get answers?




© 2011 Autodesk
How do we get answers?

   Use a variety of resources
        Using the product




© 2011 Autodesk
How do we get answers?

   Use a variety of resources
     Using the product
     Help documentation




© 2011 Autodesk
How do we get answers?

   Use a variety of resources
     Using the product
     Help documentation
     Bug tracking systems




© 2011 Autodesk
How do we get answers?

   Use a variety of resources
     Using the product
     Help documentation
     Bug tracking systems
     White papers




© 2011 Autodesk
How do we get answers?

   Use a variety of resources
        Using the product
        Help documentation
        Bug tracking systems
        White papers
        Google!




© 2011 Autodesk
What do we want from Help Files?




© 2011 Autodesk
What do we want from Help Files?

   Reliable




© 2011 Autodesk
What do we want from Help Files?

   Reliable
   Up to Date




© 2011 Autodesk
What do we want from Help Files?

   Reliable
   Up to Date
   Searchable
        Lots of keywords, across geo’s




© 2011 Autodesk
What do we want from Help Files?

   Reliable
   Up to Date
   Searchable
        Lots of keywords, across geo’s
   Reusable
        For blogs, technical solutions…




© 2011 Autodesk
What do we want from Help Files?

   Reliable
   Up to Date
   Searchable
        Lots of keywords, across geo’s
   Reusable
        For blogs, technical solutions…
   Simple linking




© 2011 Autodesk
What do we want from Help Files?

   Reliable
   Up to Date
   Searchable
        Lots of keywords, across geo’s
   Reusable
        For blogs, technical solutions…
   Simple linking
        Helping the customer to fish




© 2011 Autodesk
Be aware of the range of environments
  Terminology Varies
                                   Buildings



                        Factory
                                                Ships
                       machinery



                                   NAVISWORKS




                         Cars                   Planes



                                    Oil Rigs




© 2011 Autodesk
What do we want from wikis?




© 2011 Autodesk
What do we want from wikis?

   Ability to change or correct it
        You’re not alone!




© 2011 Autodesk
What do we want from wikis?

   Ability to change or correct it
        You’re not alone!
   Feed back into the product




© 2011 Autodesk
What do we want from wikis?

   Ability to change or correct it
        You’re not alone!
   Feed back into the product
   Check statistics
     Search results
     Page hits
     Where from?




© 2011 Autodesk
What do we want from wikis?

   Ability to change or correct it
        You’re not alone!
   Feed back into the product
   Check statistics
     Search results
     Page hits
     Where from?
   Get meaningful feedback
     Add comment forms
     Add surveys




© 2011 Autodesk
What do we want for international users?




© 2011 Autodesk
What do we want for international users?

   Translated help files, technical translation




© 2011 Autodesk
What do we want for international users?

   Translated help files, technical translation
   Access to translations
   Include regional issues




© 2011 Autodesk
What do we want from tooltips?




© 2011 Autodesk
What do we want from tooltips?

   The how to rather than why
   Images
   Videos
   Internationally understandable
        Symbols or translations




© 2011 Autodesk
What do we want from videos?




© 2011 Autodesk
What do we want from videos?

   We want to use them!
     We want to explain concepts
     We want to put things in context




© 2011 Autodesk
What do we want from videos?

   We want to use them!
     We want to explain concepts
     We want to put things in context
   Need to be accessible to all




© 2011 Autodesk
What do we want from videos?

   We want to use them!
     We want to explain concepts
     We want to put things in context
   Need to be accessible to all
   Create playlists for workflows
     Perfect for installation and setup!
     Most popular page in support!




© 2011 Autodesk
What do we want from your extra knowledge?




© 2011 Autodesk
What do we want from your extra knowledge?

   You have lots of information
   Doesn’t have to be formally presented or perfect…
    just accessible!
        Wikis
        Specifications
        Tech notes
        Known Issues
        Searchable




© 2011 Autodesk
What do we want to do?




© 2011 Autodesk
What do we want to do?

   Do we have the answer?
   Can they find the answer?
   Can we find the answer?
   Can we send them the answer?
   We want to avoid this
   And more of this




© 2011 Autodesk
Me!

                  Personal Twitter ramblings @leeroyb
                  Work Twitter ramblings @navisworks
                  LinkedIn - www.linkedin.com/in/lrmullin
                  blogs.autodesk.com/beyonddesign
                  lee.mullin@autodesk.com




© 2011 Autodesk
The end!




© 2011 Autodesk

More Related Content

Viewers also liked

Weekly events for classroom
Weekly events for classroomWeekly events for classroom
Weekly events for classroomAshley Gionta
 
Forum baik buruk internet
Forum baik buruk internetForum baik buruk internet
Forum baik buruk internetkinombura chee
 
The antecedents of language development
The antecedents of language developmentThe antecedents of language development
The antecedents of language developmentCorban Olores
 
Teori + Jurnal = Rumusan
Teori + Jurnal = RumusanTeori + Jurnal = Rumusan
Teori + Jurnal = Rumusankinombura chee
 
Ppt185.pptm [autoguardado]
Ppt185.pptm [autoguardado]Ppt185.pptm [autoguardado]
Ppt185.pptm [autoguardado]England12
 
Супрунова Е. Г.
Супрунова Е. Г.Супрунова Е. Г.
Супрунова Е. Г.Denis_0026
 
Фоминская Е. Г.
Фоминская Е. Г.Фоминская Е. Г.
Фоминская Е. Г.Denis_0026
 
Фоминская Е. Г.
Фоминская Е. Г.Фоминская Е. Г.
Фоминская Е. Г.Denis_0026
 
behaviour & discipline mgt
behaviour & discipline mgtbehaviour & discipline mgt
behaviour & discipline mgtkinombura chee
 
Marketing Quick Start Guide
Marketing Quick Start Guide Marketing Quick Start Guide
Marketing Quick Start Guide Act-On Software
 
UMTS UTRAN Call Flow
UMTS UTRAN Call FlowUMTS UTRAN Call Flow
UMTS UTRAN Call FlowSujeet Kumar
 
WCDMA Air Interface
WCDMA Air InterfaceWCDMA Air Interface
WCDMA Air InterfaceSujeet Kumar
 

Viewers also liked (14)

Weekly events for classroom
Weekly events for classroomWeekly events for classroom
Weekly events for classroom
 
Assalamu’alaikum wr
Assalamu’alaikum wrAssalamu’alaikum wr
Assalamu’alaikum wr
 
Forum baik buruk internet
Forum baik buruk internetForum baik buruk internet
Forum baik buruk internet
 
The antecedents of language development
The antecedents of language developmentThe antecedents of language development
The antecedents of language development
 
Teori + Jurnal = Rumusan
Teori + Jurnal = RumusanTeori + Jurnal = Rumusan
Teori + Jurnal = Rumusan
 
Ppt185.pptm [autoguardado]
Ppt185.pptm [autoguardado]Ppt185.pptm [autoguardado]
Ppt185.pptm [autoguardado]
 
Супрунова Е. Г.
Супрунова Е. Г.Супрунова Е. Г.
Супрунова Е. Г.
 
Фоминская Е. Г.
Фоминская Е. Г.Фоминская Е. Г.
Фоминская Е. Г.
 
Фоминская Е. Г.
Фоминская Е. Г.Фоминская Е. Г.
Фоминская Е. Г.
 
Accidentes de transito
Accidentes de transito Accidentes de transito
Accidentes de transito
 
behaviour & discipline mgt
behaviour & discipline mgtbehaviour & discipline mgt
behaviour & discipline mgt
 
Marketing Quick Start Guide
Marketing Quick Start Guide Marketing Quick Start Guide
Marketing Quick Start Guide
 
UMTS UTRAN Call Flow
UMTS UTRAN Call FlowUMTS UTRAN Call Flow
UMTS UTRAN Call Flow
 
WCDMA Air Interface
WCDMA Air InterfaceWCDMA Air Interface
WCDMA Air Interface
 

Similar to What do Technical Support want from Technical Communicators

SharePoint2010Integration
SharePoint2010IntegrationSharePoint2010Integration
SharePoint2010IntegrationSlava Gorbunov
 
GrabCAD CrowdSourcing in Design and Engineering
GrabCAD CrowdSourcing in Design and EngineeringGrabCAD CrowdSourcing in Design and Engineering
GrabCAD CrowdSourcing in Design and EngineeringHardi Meybaum
 
Starting mobile development
Starting mobile developmentStarting mobile development
Starting mobile developmentMihai Corlan
 
Microsoft The future of productivity - 22 juni 2012
Microsoft   The future of productivity - 22 juni 2012Microsoft   The future of productivity - 22 juni 2012
Microsoft The future of productivity - 22 juni 2012Ingram Micro Nederland
 
AU2012_AB2006_presentation
AU2012_AB2006_presentationAU2012_AB2006_presentation
AU2012_AB2006_presentationpchan925
 
HTML5 based PivotViewer for Visualizing LInked Data
HTML5 based PivotViewer for Visualizing LInked Data HTML5 based PivotViewer for Visualizing LInked Data
HTML5 based PivotViewer for Visualizing LInked Data Kingsley Uyi Idehen
 
Extend your reach - making your website accessible to everyone
Extend your reach - making your website accessible to everyoneExtend your reach - making your website accessible to everyone
Extend your reach - making your website accessible to everyoneMike Osborne
 
Converge SE 2011 Building a Strong Foundation
Converge SE 2011 Building a Strong FoundationConverge SE 2011 Building a Strong Foundation
Converge SE 2011 Building a Strong FoundationAaron Quinn
 
Tony Wood - Keynote Vision with Technology
Tony Wood - Keynote Vision with TechnologyTony Wood - Keynote Vision with Technology
Tony Wood - Keynote Vision with TechnologyeZ Publish Community
 
Adobe MAX 2015 - Giving Flash Professional Another Look
Adobe MAX 2015 - Giving Flash Professional Another LookAdobe MAX 2015 - Giving Flash Professional Another Look
Adobe MAX 2015 - Giving Flash Professional Another LookJoseph Labrecque
 
Reasons for Flash: Flash Development in an HTML5 and App Store World
Reasons for Flash: Flash Development in an HTML5 and App Store WorldReasons for Flash: Flash Development in an HTML5 and App Store World
Reasons for Flash: Flash Development in an HTML5 and App Store WorldEffectiveUI
 
Android Development: Approach for Agile Teams
Android Development: Approach for Agile TeamsAndroid Development: Approach for Agile Teams
Android Development: Approach for Agile TeamsAnay Kamat
 
Sales Efficiency through Simplification (Autodesk)
Sales Efficiency through Simplification (Autodesk)Sales Efficiency through Simplification (Autodesk)
Sales Efficiency through Simplification (Autodesk)SAVO
 
Exposing_Capella_Models_to_OSLC_Consumers.pdf
Exposing_Capella_Models_to_OSLC_Consumers.pdfExposing_Capella_Models_to_OSLC_Consumers.pdf
Exposing_Capella_Models_to_OSLC_Consumers.pdfmiaoli35
 
Oracle WebLogic Server 12.2.1 Do More with Less
Oracle WebLogic Server 12.2.1 Do More with LessOracle WebLogic Server 12.2.1 Do More with Less
Oracle WebLogic Server 12.2.1 Do More with LessEd Burns
 
Sustainable Design
Sustainable Design Sustainable Design
Sustainable Design AMEE
 

Similar to What do Technical Support want from Technical Communicators (20)

SharePoint2010Integration
SharePoint2010IntegrationSharePoint2010Integration
SharePoint2010Integration
 
GrabCAD CrowdSourcing in Design and Engineering
GrabCAD CrowdSourcing in Design and EngineeringGrabCAD CrowdSourcing in Design and Engineering
GrabCAD CrowdSourcing in Design and Engineering
 
Starting mobile development
Starting mobile developmentStarting mobile development
Starting mobile development
 
Microsoft The future of productivity - 22 juni 2012
Microsoft   The future of productivity - 22 juni 2012Microsoft   The future of productivity - 22 juni 2012
Microsoft The future of productivity - 22 juni 2012
 
AU2012_AB2006_presentation
AU2012_AB2006_presentationAU2012_AB2006_presentation
AU2012_AB2006_presentation
 
Amaze Futures Sessions
Amaze Futures SessionsAmaze Futures Sessions
Amaze Futures Sessions
 
HTML5 based PivotViewer for Visualizing LInked Data
HTML5 based PivotViewer for Visualizing LInked Data HTML5 based PivotViewer for Visualizing LInked Data
HTML5 based PivotViewer for Visualizing LInked Data
 
Extend your reach - making your website accessible to everyone
Extend your reach - making your website accessible to everyoneExtend your reach - making your website accessible to everyone
Extend your reach - making your website accessible to everyone
 
Converge SE 2011 Building a Strong Foundation
Converge SE 2011 Building a Strong FoundationConverge SE 2011 Building a Strong Foundation
Converge SE 2011 Building a Strong Foundation
 
Tony Wood - Keynote Vision with Technology
Tony Wood - Keynote Vision with TechnologyTony Wood - Keynote Vision with Technology
Tony Wood - Keynote Vision with Technology
 
Adobe MAX 2015 - Giving Flash Professional Another Look
Adobe MAX 2015 - Giving Flash Professional Another LookAdobe MAX 2015 - Giving Flash Professional Another Look
Adobe MAX 2015 - Giving Flash Professional Another Look
 
Ma forge++ : @Cloud
Ma forge++ : @CloudMa forge++ : @Cloud
Ma forge++ : @Cloud
 
ELIA Lyon 2015 Static
ELIA Lyon 2015 StaticELIA Lyon 2015 Static
ELIA Lyon 2015 Static
 
Recruiting 2.0 Avanade
Recruiting 2.0 AvanadeRecruiting 2.0 Avanade
Recruiting 2.0 Avanade
 
Reasons for Flash: Flash Development in an HTML5 and App Store World
Reasons for Flash: Flash Development in an HTML5 and App Store WorldReasons for Flash: Flash Development in an HTML5 and App Store World
Reasons for Flash: Flash Development in an HTML5 and App Store World
 
Android Development: Approach for Agile Teams
Android Development: Approach for Agile TeamsAndroid Development: Approach for Agile Teams
Android Development: Approach for Agile Teams
 
Sales Efficiency through Simplification (Autodesk)
Sales Efficiency through Simplification (Autodesk)Sales Efficiency through Simplification (Autodesk)
Sales Efficiency through Simplification (Autodesk)
 
Exposing_Capella_Models_to_OSLC_Consumers.pdf
Exposing_Capella_Models_to_OSLC_Consumers.pdfExposing_Capella_Models_to_OSLC_Consumers.pdf
Exposing_Capella_Models_to_OSLC_Consumers.pdf
 
Oracle WebLogic Server 12.2.1 Do More with Less
Oracle WebLogic Server 12.2.1 Do More with LessOracle WebLogic Server 12.2.1 Do More with Less
Oracle WebLogic Server 12.2.1 Do More with Less
 
Sustainable Design
Sustainable Design Sustainable Design
Sustainable Design
 

What do Technical Support want from Technical Communicators

  • 1. What do Technical Support want from Technical Communicators Lee Mullin Premium Support Specialist - Autodesk © 2011 Autodesk
  • 2. About Me – Lee Mullin  Autodesk support for over 7 years © 2011 Autodesk
  • 3. About Me – Lee Mullin  Autodesk support for over 7 years  Autodesk blogger © 2011 Autodesk
  • 4. About Me – Lee Mullin  Autodesk support for over 7 years  Autodesk blogger  Live in Sheffield, UK © 2011 Autodesk
  • 5. About Me – Lee Mullin  Autodesk support for over 7 years  Autodesk blogger  Live in Sheffield, UK  Hobbies  Walking © 2011 Autodesk
  • 6. About Me – Lee Mullin  Autodesk support for over 7 years  Autodesk blogger  Live in Sheffield, UK  Hobbies  Walking  Watching sports © 2011 Autodesk
  • 7. About Me – Lee Mullin  Autodesk support for over 7 years  Autodesk blogger  Live in Sheffield, UK  Hobbies  Walking  Watching sports  Live music © 2011 Autodesk
  • 8. Who do we speak to in support? © 2011 Autodesk
  • 9. Who do we speak to?  Calm customers © 2011 Autodesk
  • 10. Who do we speak to?  Calm customers  Angry customers © 2011 Autodesk
  • 11. Who do we speak to?  Calm customers  Angry customers  Big customers © 2011 Autodesk
  • 12. Who do we speak to?  Calm customers  Angry customers  Big customers  Small customers © 2011 Autodesk
  • 13. Who do we speak to?  Calm customers  Angry customers  Big customers  Small customers  Internal customers © 2011 Autodesk
  • 14. Who do we speak to?  Calm customers  Angry customers  Big customers  Small customers  Internal customers  External customers © 2011 Autodesk
  • 15. Who do we speak to?  Calm customers  Angry customers  Big customers  Small customers  Internal customers  External customers  Intelligent customers © 2011 Autodesk
  • 16. Who do we speak to?  Calm customers  Angry customers  Big customers  Small customers  Internal customers  External customers  Intelligent customers  And less intelligent © 2011 Autodesk
  • 17. What do customers want? © 2011 Autodesk
  • 18. What do customers want?  Answers  Fixes  FAST © 2011 Autodesk
  • 19. Why do they want answers? © 2011 Autodesk
  • 20. Why do they want answers?  They can’t find the answer easily © 2011 Autodesk
  • 21. Why do they want answers?  They can’t be bothered looking for an answer © 2011 Autodesk
  • 22. Why do they want answers? The answer isn’t available © 2011 Autodesk
  • 23. How do we get answers? © 2011 Autodesk
  • 24. How do we get answers?  Use a variety of resources  Using the product © 2011 Autodesk
  • 25. How do we get answers?  Use a variety of resources  Using the product  Help documentation © 2011 Autodesk
  • 26. How do we get answers?  Use a variety of resources  Using the product  Help documentation  Bug tracking systems © 2011 Autodesk
  • 27. How do we get answers?  Use a variety of resources  Using the product  Help documentation  Bug tracking systems  White papers © 2011 Autodesk
  • 28. How do we get answers?  Use a variety of resources  Using the product  Help documentation  Bug tracking systems  White papers  Google! © 2011 Autodesk
  • 29. What do we want from Help Files? © 2011 Autodesk
  • 30. What do we want from Help Files?  Reliable © 2011 Autodesk
  • 31. What do we want from Help Files?  Reliable  Up to Date © 2011 Autodesk
  • 32. What do we want from Help Files?  Reliable  Up to Date  Searchable  Lots of keywords, across geo’s © 2011 Autodesk
  • 33. What do we want from Help Files?  Reliable  Up to Date  Searchable  Lots of keywords, across geo’s  Reusable  For blogs, technical solutions… © 2011 Autodesk
  • 34. What do we want from Help Files?  Reliable  Up to Date  Searchable  Lots of keywords, across geo’s  Reusable  For blogs, technical solutions…  Simple linking © 2011 Autodesk
  • 35. What do we want from Help Files?  Reliable  Up to Date  Searchable  Lots of keywords, across geo’s  Reusable  For blogs, technical solutions…  Simple linking  Helping the customer to fish © 2011 Autodesk
  • 36. Be aware of the range of environments Terminology Varies Buildings Factory Ships machinery NAVISWORKS Cars Planes Oil Rigs © 2011 Autodesk
  • 37. What do we want from wikis? © 2011 Autodesk
  • 38. What do we want from wikis?  Ability to change or correct it  You’re not alone! © 2011 Autodesk
  • 39. What do we want from wikis?  Ability to change or correct it  You’re not alone!  Feed back into the product © 2011 Autodesk
  • 40. What do we want from wikis?  Ability to change or correct it  You’re not alone!  Feed back into the product  Check statistics  Search results  Page hits  Where from? © 2011 Autodesk
  • 41. What do we want from wikis?  Ability to change or correct it  You’re not alone!  Feed back into the product  Check statistics  Search results  Page hits  Where from?  Get meaningful feedback  Add comment forms  Add surveys © 2011 Autodesk
  • 42. What do we want for international users? © 2011 Autodesk
  • 43. What do we want for international users?  Translated help files, technical translation © 2011 Autodesk
  • 44. What do we want for international users?  Translated help files, technical translation  Access to translations  Include regional issues © 2011 Autodesk
  • 45. What do we want from tooltips? © 2011 Autodesk
  • 46. What do we want from tooltips?  The how to rather than why  Images  Videos  Internationally understandable  Symbols or translations © 2011 Autodesk
  • 47. What do we want from videos? © 2011 Autodesk
  • 48. What do we want from videos?  We want to use them!  We want to explain concepts  We want to put things in context © 2011 Autodesk
  • 49. What do we want from videos?  We want to use them!  We want to explain concepts  We want to put things in context  Need to be accessible to all © 2011 Autodesk
  • 50. What do we want from videos?  We want to use them!  We want to explain concepts  We want to put things in context  Need to be accessible to all  Create playlists for workflows  Perfect for installation and setup!  Most popular page in support! © 2011 Autodesk
  • 51. What do we want from your extra knowledge? © 2011 Autodesk
  • 52. What do we want from your extra knowledge?  You have lots of information  Doesn’t have to be formally presented or perfect… just accessible!  Wikis  Specifications  Tech notes  Known Issues  Searchable © 2011 Autodesk
  • 53. What do we want to do? © 2011 Autodesk
  • 54. What do we want to do?  Do we have the answer?  Can they find the answer?  Can we find the answer?  Can we send them the answer?  We want to avoid this  And more of this © 2011 Autodesk
  • 55. Me! Personal Twitter ramblings @leeroyb Work Twitter ramblings @navisworks LinkedIn - www.linkedin.com/in/lrmullin blogs.autodesk.com/beyonddesign lee.mullin@autodesk.com © 2011 Autodesk
  • 56. The end! © 2011 Autodesk

Editor's Notes

  1. Hi, I’m Lee Mullin, I’ve been the lead support technician for Navisworks for several years, starting in 2005. I’m the lead author of the Beyond Design blog, a resource for construction professionals using Revit, Navisworks and QTO.I live in Sheffield in the United Kingdom and my hobbies include promoting and watching live music, long walks in the country and watching sports like football and Formula one
  2. Hi, I’m Lee Mullin, I’ve been the lead support technician for Navisworks for several years, starting in 2005. I’m the lead author of the Beyond Design blog, a resource for construction professionals using Revit, Navisworks and QTO.I live in Sheffield in the United Kingdom and my hobbies include promoting and watching live music, long walks in the country and watching sports like football and Formula one
  3. Hi, I’m Lee Mullin, I’ve been the lead support technician for Navisworks for several years, starting in 2005. I’m the lead author of the Beyond Design blog, a resource for construction professionals using Revit, Navisworks and QTO.I live in Sheffield in the United Kingdom and my hobbies include promoting and watching live music, long walks in the country and watching sports like football and Formula one
  4. Hi, I’m Lee Mullin, I’ve been the lead support technician for Navisworks for several years, starting in 2005. I’m the lead author of the Beyond Design blog, a resource for construction professionals using Revit, Navisworks and QTO.I live in Sheffield in the United Kingdom and my hobbies include promoting and watching live music, long walks in the country and watching sports like football and Formula one
  5. Hi, I’m Lee Mullin, I’ve been the lead support technician for Navisworks for several years, starting in 2005. I’m the lead author of the Beyond Design blog, a resource for construction professionals using Revit, Navisworks and QTO.I live in Sheffield in the United Kingdom and my hobbies include promoting and watching live music, long walks in the country and watching sports like football and Formula one
  6. Hi, I’m Lee Mullin, I’ve been the lead support technician for Navisworks for several years, starting in 2005. I’m the lead author of the Beyond Design blog, a resource for construction professionals using Revit, Navisworks and QTO.I live in Sheffield in the United Kingdom and my hobbies include promoting and watching live music, long walks in the country and watching sports like football and Formula one