<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:g-custom="http://base.google.com/cns/1.0" xmlns:media="http://search.yahoo.com/mrss/" version="2.0">
  <channel>
    <title>montytec-services</title>
    <link>https://www.montytec.digital</link>
    <description />
    <atom:link href="https://www.montytec.digital/feed/rss2" type="application/rss+xml" rel="self" />
    <item>
      <title>Building great product engineering teams</title>
      <link>https://www.montytec.digital/building-great-product-engineering-teams</link>
      <description />
      <content:encoded>&lt;div data-rss-type="text"&gt;&#xD;
  &lt;h3&gt;&#xD;
    &lt;span&gt;&#xD;
      
           Step 1 - Understanding where you are today
          &#xD;
    &lt;/span&gt;&#xD;
  &lt;/h3&gt;&#xD;
  &lt;p&gt;&#xD;
    &lt;span&gt;&#xD;
      &lt;span&gt;&#xD;
        
            One of the first things you need to do before moving forward with a plan to improve your team is building an understanding of where you are today.
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/span&gt;&#xD;
  &lt;/p&gt;&#xD;
&lt;/div&gt;&#xD;
&lt;div&gt;&#xD;
  &lt;img src="https://irp.cdn-website.com/53ea4921/dms3rep/multi/Building-teams---Mind-Map--281-29.jpg"/&gt;&#xD;
&lt;/div&gt;&#xD;
&lt;div data-rss-type="text"&gt;&#xD;
  &lt;p&gt;&#xD;
    &lt;span&gt;&#xD;
      
           The things driving you inside the team and the drivers you have external to the team.
          &#xD;
    &lt;/span&gt;&#xD;
  &lt;/p&gt;&#xD;
  &lt;ul&gt;&#xD;
    &lt;li&gt;&#xD;
      &lt;span&gt;&#xD;
        
            Do you have a preferred and defined tech stack?
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/li&gt;&#xD;
    &lt;li&gt;&#xD;
      &lt;span&gt;&#xD;
        
            Does your team communicate well internally and externally?
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/li&gt;&#xD;
    &lt;li&gt;&#xD;
      &lt;span&gt;&#xD;
        
            How does work flow into the team?
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/li&gt;&#xD;
    &lt;li&gt;&#xD;
      &lt;span&gt;&#xD;
        
            etc.
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/li&gt;&#xD;
  &lt;/ul&gt;&#xD;
  &lt;p&gt;&#xD;
    &lt;span&gt;&#xD;
      &lt;span&gt;&#xD;
        
            I have always found mind-maps are great tool for visualising something like this, in this case capturing some of the key influences and considerations that impact building great teams.
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/span&gt;&#xD;
  &lt;/p&gt;&#xD;
  &lt;p&gt;&#xD;
    &lt;span&gt;&#xD;
      &lt;span&gt;&#xD;
        
            To explore the full mind-map in miro click
           &#xD;
      &lt;/span&gt;&#xD;
    &lt;/span&gt;&#xD;
    &lt;span&gt;&#xD;
      
           see the board
          &#xD;
    &lt;/span&gt;&#xD;
    &lt;span&gt;&#xD;
      &lt;span&gt;&#xD;
        
            below. Feel free to duplicate and map out where your teams sit today.
            &#xD;
        &lt;span&gt;&#xD;
          
             ﻿
            &#xD;
        &lt;/span&gt;&#xD;
      &lt;/span&gt;&#xD;
    &lt;/span&gt;&#xD;
  &lt;/p&gt;&#xD;
  &lt;p&gt;&#xD;
    &lt;span&gt;&#xD;
      
           I will also be pulling this into an online survey / questionnaire if people are interested get in 
          &#xD;
    &lt;/span&gt;&#xD;
    &lt;a href="/contact"&gt;&#xD;
      
           touch
          &#xD;
    &lt;/a&gt;&#xD;
    &lt;span&gt;&#xD;
      
           .
          &#xD;
    &lt;/span&gt;&#xD;
  &lt;/p&gt;&#xD;
&lt;/div&gt;</content:encoded>
      <enclosure url="https://irp.cdn-website.com/md/pexels/dms3rep/multi/pexels-photo-3178818.jpeg" length="771961" type="image/jpeg" />
      <pubDate>Tue, 15 Feb 2022 10:07:17 GMT</pubDate>
      <author>greg@ideaorbits.com (Greg Montgomery)</author>
      <guid>https://www.montytec.digital/building-great-product-engineering-teams</guid>
      <g-custom:tags type="string" />
      <media:content medium="image" url="https://irp.cdn-website.com/md/pexels/dms3rep/multi/pexels-photo-3178818.jpeg">
        <media:description>thumbnail</media:description>
      </media:content>
      <media:content medium="image" url="https://irp.cdn-website.com/md/pexels/dms3rep/multi/pexels-photo-3178818.jpeg">
        <media:description>main image</media:description>
      </media:content>
    </item>
    <item>
      <title>What does a Consulting CTO do?</title>
      <link>https://www.montytec.digital/what-does-a-consulting-cto-do</link>
      <description />
      <content:encoded>&lt;h3&gt;&#xD;
  
         Enjoy Wellington coffee is a good start
        &#xD;
&lt;/h3&gt;&#xD;
&lt;div&gt;&#xD;
  &lt;img src="https://irp.cdn-website.com/53ea4921/dms3rep/multi/IMG_0870-fbed7795.JPG"/&gt;&#xD;
&lt;/div&gt;&#xD;
&lt;div data-rss-type="text"&gt;&#xD;
  
         Some of the best discussions are over a coffee or another appropriate beverage. As a consulting CTO it is critical to spend time listening and understanding the space you are working in, the challenges and history of where you have been.
        &#xD;
&lt;/div&gt;</content:encoded>
      <enclosure url="https://irp.cdn-website.com/md/dmip/dms3rep/multi/computer-men-work.jpg" length="182524" type="image/jpeg" />
      <pubDate>Thu, 28 Oct 2021 09:47:37 GMT</pubDate>
      <author>greg@ideaorbits.com (Greg Montgomery)</author>
      <guid>https://www.montytec.digital/what-does-a-consulting-cto-do</guid>
      <g-custom:tags type="string" />
      <media:content medium="image" url="https://irp.cdn-website.com/53ea4921/dms3rep/multi/IMG_0870.JPG">
        <media:description>thumbnail</media:description>
      </media:content>
      <media:content medium="image" url="https://irp.cdn-website.com/md/dmip/dms3rep/multi/computer-men-work.jpg">
        <media:description>main image</media:description>
      </media:content>
    </item>
  </channel>
</rss>
