This edited podcast was recorded Saturday July 28, 2017. Hosts Jay Leask and Craig Jahnke jump right into some news and then kick off our show with guest Matt Wade, Cloud Services Lead at H3 Solutions and founder of icansharepoint.

On the SPOT Episode 3 is here! #spotpodE3 <– join in the conversation

In today’s episode we cover:

* News (starting at 2:30)

* Interview with Matt Wade (starting at 9:50)

News (1:00)

* 12 ‘best practices’ IT should avoid at all costs – CIO Magazine

* Tell everyone that they are our customer <- you want to be partners with the business

* Say “No” or “Yes” to requests <- this can be done, but these are the resources and what it costs

* IT charge-backs <- leads groups to use freeware or go around IT

*  Booze Allen Hamilton developing business application for the Halo Lens (5:35)

Interview with Matt Wade (9:50)

Matt Wade | H3 Solutions | @thatmattwade

The below is the transcript of Jay and Craig’s conversation with Matt Wade, the answers are his own words.  This is an edited version of the full conversation.  The full 45-minute version of the interview can be heard here:

Who is Matt Wade?

Matt Wade:  So, I’m an engineer turned SharePoint geek. I started my career in 2009 as a mechanical engineer working for the Nuclear Navy, designing some mechanical systems on nuclear reactors going into a training platform and a little bit of work on, we probably seen it in the news lately, with the Gerald R. Ford class carrier. The first carrier going out is Ford and like kind of cool to follow the news because that was something I worked on pretty directly and I did a bunch of mechanical stuff surrounded by a lot of really smart people.

We had an issue where it was just hard to find stuff and SharePoint came out, SharePoint 2007. My dear old friend came out on our internal network which was fully classified. We had made it a very minimal internet access for most of the time that I worked there and rolled out and I kind of started playing around with document libraries, metadata, that kind of thing. And we had documents that we used as resources that dated back to before my parents were born. So, being to organize stuff by project name, component type, classification, year, and doing just whole sort filter group making views like– it was a really powerful tool for us. We had one central repository for all of our documents internally that were like issued and published but this was more of a local wrist of lengths that pointed to that and I just added our metadata to it and we were blowing up at the time.

We had like 15 people in my team and we tripled in size within a couple years. So, the fact that we had new people coming on and we have this new website that people could use, really worked out but I say 45 people– our network was 15,000 across the world from Honolulu to actually the British Isles. And the IT team had a whole bunch of work basically they needed to do for adoption stuff and th...