Your web browser is out of date. Update your browser for more security, speed and the best experience on this site.

Update your browser
CapTech Home Page

CapTech Trends Podcast Series

Thought Leaders Are Made Not Born

In this episode of CapTech Trends, CapTech CTO, Vinnie Schoenfelder discusses how to become a thought leader with CapTech Technical Director, Mark Broski. Mark is passionate about fostering academic growth (from his previous experience as a university educator) and in his current role in consulting. Listen to this inspiring episode as we discuss:

  • The difference between a thought leader and a subject matter expert.
  • How you can make the conscious choice to develop your skills and become a thought leader.
  • Why becoming a successful thought leader requires being uncomfortable and taking risks.
  • Why there is not a single thought leader archetype.
  • The common traits and patterns of behavior among successful thought leaders.
  • How organizations can embrace the development of thought leaders through their company culture.

Books referenced in this episode:



      View the transcript

      Subscribe to the CapTech Trends Podcast Series

      Apple Podcasts

      Spotify

      Google Podcasts

      Pocket Casts

      Featuring

      Vinnie Schoenfelder

      Principal, CTO

      Vinnie is a Principal at CapTech and plays a large role in helping define services, forge partnerships, and lead innovation for our clients. As a thought leader, he regularly helps clients solve their most complex business challenges.

      LinkedIn Envelope
      Mark Broski

      Mark Broski

      Technical Director

      Mark is a senior architect bringing a strong focus on quality architecture and delivery with expertise in Dev-Ops, and unit testing. His doctoral-level training in economics brings advanced modeling capabilities to complex business applications. His broad range of industry experience and excellent communication skills allow him to effectively communicate with all levels of management for both technical and non-technical stakeholders.

      Envelope