Join me on Apr 30-May 2, 2024 as I’m presenting “Understanding Microsoft 365 Copilot Extensibility Via Microsoft Graph Connectors” at the Microsoft 365 Community Conference. Registration is still open and there are pre/post workshops also available. Great to see so many subject matter experts sharing on topics related to Microsoft 365, Copilot for Microsoft 365, Azure, Dynamics, and more. My specific session will be on Wednesday May 1st, 2024 at 10-11am ET. Look forward to seeing you there!
Use this attendee discount code to save $100 USD off registration: MSCMTY
Join me on Feb 28-29, 2024 as I’m presenting “Expanding knowledge with Graph connectors” at the Copilot for Microsoft 365 Tech Accelerator event. This free, online event will have numerous subject matter experts sharing on topics related to Copilot for Microsoft 365. My specific session will be on Feb 29, 9-9:30am PT. Look forward to seeing you there!
For the past few years I have been making good use of my home office treadmill (Treadly 2) as well as biking with my kids. In 2023 I increased the number of days of exercise (33% of days up to 45%) as well as total distance for the year.
I don’t have specific goals for 2024 but looking to continue my exercise (2-4 days a week on treadmill for 60-80 mins).
Reading
Since 2021 I have been reading books more regularly. You can view my profile on GoodReads along with “read” and “want to read” lists. I set my 2023 GoodReads challenge to read 8 books and ended at reading 12. I was on track to read more but with my Diaconate classes (more on that next) my time was wrapped in classwork and required reading for my class for half of the year. A few noteworthy books from 2023:
I had previously read The 5 Love Languages with my wife. This book takes those same “languages” but adapts to them to the workplace. I actually used the lessons from this book in an org-wide initiative about Feeling Recognition. I was happy to have direct application from book to real-world in this case.
I read this book as part of a book club within my larger group at work. I found this an interesting read compared to John Doerr’s Measure What Matters. We had many lively discussions about how to apply these concepts to our semester planning and OKR settings.
For my 2024 GoodReads challenge I’ve set a goal to read 8 books again.
Diaconate classes
For the past 4+ years I’ve had reflections on my personal calling to become a deacon within the Catholic Church. I’ve been very active in various groups and ministries throughout my life, but in these past few years this has come up more regularly.
After speaking with a few deacons at our church, my wife and I finally decided to meet with the deacon in charge of formation in our diocese. He was very open and supportive of my interests and had great points for further reflection.
Currently I am in the inquirer phase and have taken 2 pre-requisite classes and just about to start my 3rd class. The whole experience has been very fulfilling as well as helping me adopt a few daily good habits that lead to improved overall well-being. I am continuing in my discernment, but any major next steps won’t happen until 2025-2026.
Copilot for Microsoft 365
In my role at Microsoft, our Microsoft Graph Customer and Partner Experience team made a large shift in priorities around May 2023 to expand our coverage of Microsoft 365 developer integrations, specifically with Copilot for Microsoft 365. This included expanding our Microsoft Graph TAP to rebrand as the Microsoft 365 Developer TAP and incorporate Copilot extensibility topics.
This has been quite the whirlwind for the past 8+ months but exciting times to be at the forefront of this new AI technology offerings. 2024 will continue with these investments across my individual team and larger org.
Family
As you might have noticed, I slowed down on blogging in 2023. This was primarily related to the above two items of Diaconate classes and Copilot for M365 work, but also to increases in involvements with my family. I’m a den leader for my son’s Cub Scout den, fill-in for coaching various sports teams my kids are on, as well as volunteering for different church programs and events. Combined with my wife returning to work part time the end of last year and that left little time for side projects with blogging.
My wife and I also celebrated our 10 yr wedding anniversary. We took a wonderful 6-day trip out to Arizona and had the most amazing time with hiking, train ride, music, and good meals.
I’ll revisit blogging and videos more regularly in the future, but for now you can take a look at 2 Copilot & Graph connectors videos I produced with our marketing team in 2023.
Extend Copilot for Microsoft 365 with external data with Graph connectors
Use Microsoft Graph Connectors To Integrate External Data With Microsoft 365
Conclusion
2023 was a packed year with new experiences, family events, and more. I hope you had a joy-filled year and grew personally and professionally. Feel free to share any of your experiences in the comments or link to your own reflection from 2023. Looking forward to all that 2024 has to offer.
If you don’t communicate the results, how are you growing / learning / improving?
Personal story
For years my wife and / or I have enjoyed hosting various events (ex. friends Thanksgiving meal, board game night, camping trip, etc.) During the pandemic we stopped hosting many of those events. Fast-forward to the past year and separate friends made comments about feeling left out at not being invited to these types of events (thinking we had continued to host but not invited them). Our lack of communication led to misunderstandings.
Applications to work
Recently I completed the Growth Series program from Reforge. One of the modules covers experimentation. The idea presented is that our growth system has a cycle of:
Growth model – Growing engagement, retention, etc.
User Psychology – Understand our users and how they make decisions
Experimentation – Tweaking variables to improve our product and reinforce growth model
Through the process of running experiments, we need to communicate out the results, otherwise it breaks the cycle and leads to a useless process. This can apply to experiments run, feedback gathered, or status on OKRs (objectives and key results), and more.
Methods for communication
How and what you communicate will depend on a number of factors.
Asynchronous or synchronous?
Targeted or broad audience?
Narrative story or metrics?
Etc.
For example, my Microsoft Graph CPx team has used a number of mechanisms including monthly newsletters, stakeholder briefing meetings, Power BI dashboards, customer story emails, and more.
Systems for success
Taking ideas from the book Atomic Habits, how can you set up systems for success, or what I like to affectionately call “fall into the pit of success”? Make your communication mechanisms visible, easy to complete, and easily motivated. This might include:
Setting a recurring team-level calendar reminder X days before due date
Create a template for how / what you want filled out
Use workflows / dashboards to collate information
Conclusion
Doing the work is important, but we must remember to complete the cycle by communicating out the results. This will help inform how we iterate and improve the next cycle. Personally, I’m keeping this in mind to improve on each project and effort I’m leading or participating in.
Please share in comments what techniques or approaches are helping you be more effective at communicating results?
This week is “Perspectives Week” (time to request or provide feedback to peers across the org / company) so I’ll share out some of my tips on how I approach this:
Where
I use our internal MSConnect tool for majority of feedback requests, but also Yammer Praise for sending kudos / feedback to people who may not have requested feedback from me.
Who
Identify a mix of people inside your group (M2, aka manager’s manager, level and below) as well as outside.
Target individuals in varying roles (ex. marketing, engineering, sales, etc.)
When
I like to request feedback 2x times per calendar year, ~2 months before my next semesterly review cycle (called a “Connect”).
This usually lands Feb-Mar and Sept-Oct. This also avoids semester planning timeframes when many teams are heads down on writing / reviewing papers.
Do not request feedback from someone more than 1x per year.
This is not a hard requirement, but I find my own feedback for someone doesn’t change drastically within a given year.
How
Customize your request for feedback.
Include specific projects / teams / work efforts that you have collaborated on to focus the person’s feedback on.
Ex. “As we have been working together on <Project X>, I would appreciate any feedback you can share on my work or areas for improvement. Thank you for your time and attention.”
Provide constructive / usable feedback.
When filling out feedback for others, take the time to share actionable or thought-provoking feedback.
Avoid “you’re doing a great job” type bland feedback.
Two final notes.
Use the feedback system that makes sense
Not everyone is comfortable with sharing feedback is an official tool. Others may prefer 1:1 chat / email / face to face.
Don’t worry if you don’t get a response
People are busy. I know a number of peers who are overwhelmed by the number of feedback requests they receive (in addition to normal work). You can “nudge” someone 1:1 if they haven’t responded on your feedback request, but also be respectful of their time.
How do you approach sharing and requesting feedback? Share your thoughts in the comments.
A huge thank you to the attendees, organizers, volunteers, sponsors, and anyone else involved with M365 Twin Cities. This was my first community conference in 3+ years but it was amazing to share more about Microsoft Graph in my two sessions. I appreciate all of the attendees who joined and had great questions and engagement.
Below are PDF copies of the slides I presented. If you have any questions, feel free to ask in the comments here or reach out to me. Look forward to presenting at more events later this year as opportunities arise.
Getting Up to Speed with Microsoft Graph Development
The Frog Pond of Technology 