Migrating over 30 RPA bots from UiPath to Power Automate Desktop was one of the most complex but rewarding projects I’ve led in recent years. What began as a technical migration turned into a powerful exercise in communication, collaboration, and clarity under pressure.

The outcome? Over $1 million in expected savings within five years and a set of lessons that apply far beyond automation projects.

In this project, I am working with multiple teams (Internal and External) within the company.

I wasn’t part of the original operations team managing these bots, yet I was asked to lead the migration. That meant stepping into a space where the systems, dependencies, and context were new, a challenge that tested both my leadership skills and adaptability.

I worked on various migration projects, although they were from SharePoint (varies from on-premises to cloud, SharePoint Designer workflows to Nintext, etc). Those experiences did help me in this project to anticipate some of the challenges.

My teammates are great help, so we can pull this migration off successfully. Always remember you are only as good as your team.

Here are the key lessons learned from this project.

1. Effective Communication

One of the most critical aspects of the migration was maintaining clear and consistent communication with all stakeholders. This included Bot Owners and Business Partners, product owner, migration team, operations team and other teams involved. Ensuring they are all informed about the migration progress is crucial during the migration.

Below are a few teams we had to work with during the migration project.

Infrastructure Teams: Coordinating the provisioning of necessary infrastructure to run and maintain the bots.

CyberArk Teams: Integrating CyberArk for secure credential management.

Cybersecurity Teams: Conducting security risk assessments.

Migration Partners: Collaborating with external partners, assisting in the migration from UiPath to Power Automate Desktop.

Operations Teams: Leveraging their existing knowledge of the bots and getting help in creating Test cases for each of the bots.

Microsoft Support Teams: Working closely with Microsoft for technical support to resolve CyberArk integration, Performance issues, etc.

Regular updates were provided to all stakeholders, ensuring everyone was aligned on the migration progress.

Communication Strategies

Effective communication strategies included are as below:

Regular Updates: Providing detailed updates on each application’s progress, from pre-migration activities to hypercare and then to operations.

Stakeholder Involvement: Ensuring all relevant stakeholders, including business partners and IT teams, were informed and aligned.

Below are the tools used for communication:

Emails, MS Forms, MS Teams, and scheduled calls were used to facilitate communication. Emails are mainly used to communicate with business users, and MS Forms are used to collect the info at the beginning of the project. MS Teams is used to communicate with almost everyone :)

To keep everyone aligned, we used:

• Weekly updates (via Teams + email summaries)

• MS Forms (to capture inputs from business users)

• Scheduled sync calls (to resolve blockers fast)

The lesson: Communication isn’t just about sharing updates, it’s about reducing uncertainty.

One of the next key challenges is having skilled team members.

2. Skilled Team Members

Having the right skilled people on the project was essential. Challenges arise when team members lack the necessary expertise, leading to delays and rework.

For example, one of the team members lacked experience with factory models, causing delays in bot completion, and a support Engineer unfamiliar with C#, Azure, and Power Platform struggled with code changes.

It’s crucial to identify skilled individuals early, provide training if needed, and escalate issues to the team you're working with to ensure the right expertise is available.

Vendor Collaboration

Trusting the vendor to provide the right team was crucial. However, it’s advisable to review the CVs of team members to ensure they have the necessary skills and experience. Starting with smaller applications before tackling complex ones helped assess the team’s capabilities.

3. Keep a Margin of Safety

When migrating from one tool to another, it’s important to account for unexpected delays. For example, licensing considerations required a buffer of three to four weeks.

One bot experienced delays, highlighting the need for a safety margin in project timelines.

We do not have an option to double the margin of safety like building bridges, but like all other IT Projects here, we did use the margin of safety to account for the surprises.

Parrish, Shane. Clear Thinking: Turning Ordinary Moments into Extraordinary Results

4. Expect Surprises (and Be Ready to Pivot)

Unexpected challenges are inevitable. For example, when a team member lacked the necessary knowledge, it made it difficult to implement changes. You need to look at exploring alternative Solutions: In this case, we did explore an option of pushing Power BI data to Dataverse using Power Automate flows instead of making code changes.

Being prepared for surprises and having contingency plans is key to overcoming unforeseen obstacles.

Unexpected Challenges

Several unexpected challenges were encountered, such as Infrastructure Dependencies, additional hard drives, firewall changes, and SAP system integrations were required.

Complex Integrations: Applications utilizing .NET chatbots, Azure app services, and Cosmos DB introduced additional complexity.

API Development: In some cases, APIs had to be developed to authenticate and perform actions in bot applications.

Always account for the surprises, but make sure you celebrate successes along the way.

5. Celebrating Successes

Celebrating milestones along the way boosts team morale. For instance, each time an application completed UAT and went live, the team celebrated.

Recognizing achievements, whether through daily stand-ups or feedback emails, helps maintain motivation throughout the project.

6. Microsoft Support

Microsoft support played a vital role in resolving challenges, such as:

CyberArk Integration: Assisting with the configuration to enable CyberArk integration.

Performance Issues: Troubleshooting internal database authentication delays.

Workflow History: Resolving issues where desktop flows were not showing workflow history.

Conclusion

Migrating RPA bots to Power Automate Desktop is a complex process that requires effective communication, skilled team members, and a proactive approach to handling challenges. By celebrating successes and maintaining a margin of safety, the project can achieve its goals while keeping the team motivated and aligned.

This project is a lift and shift from UiPath to Power Automate desktop. Once migration is complete, the plan is to incorporate the improvements and convert some of the features to cloud flows instead of using many Excel documents in the current BOTs. I will write one more blog post once the improvements are completed.

Until then, if you’ve been through a similar migration, I’d love to hear what lessons stood out for you.

Since I joined 90 day mentoring challenge last year, a lot has changed.

You can read my thoughts on mentoring challenge below.

I signed-up this Q4 again but planning to mentor others via the program.

Thank you Meg and Mark for the opportunity to make a difference.

Here are the notes from last year after i finished the 90 day mentoring challenge.

I joined Q1, 2024 90-day mentoring challenge at https://ako.nz365guy.com.

We are nearing the end of the cohort. I am sharing my thoughts on what it was like to be part of the program.

I also joined the program a few years back, but for some reason, I didn’t use it to its full potential. This program can offer a lot to you personally and professionally.

I wanted to make amends this time.

Why did I join this time?

I couldn’t make the best use of the challenge last time.

Maybe I wasn’t ready for it.

I was too busy with other things in my life.

This time though I am ready.

I am working as an independent consultant, and I wanted to learn how everyone from other places works and gets things done.

I wanted to learn from Mark, as he has extensive experience working with people around the globe and a wealth of knowledge.

Most importantly, I wanted to write and build a network with like-minded people.

How I made the decision

I am getting emails from Mark and a notification from Dani.

Given that I was on the waiting list, I am getting messages about who joined the program.

Heaps of them joined the program.

I know many people from the community who are writing and making an impact.

They do not know me yet. Of course, now they know me 😁

I wasn’t ready, as I was waiting for my current work situation.

Once that was clear.

I decided to join the challenge and learn from everyone part of the challenge.

First few weeks

I am a slow starter like a Test match player who needs time to get in, not a typical T20 person who can hit from the beginning.

Oops, sorry if you didn’t understand. It is a cricket (sports game) analogy. Well, a lot of people don’t know about it.

Everyone is sharing the intro videos, and I am getting to know more and more people in the community.

All of them have different careers and experiences.

It is great to connect with everyone on LinkedIn.

Sorry if you are in the current cohort and I didn’t connect. Please connect with me on LinkedIn.

https://www.linkedin.com/in/devendravelegandla/

What’s connecting all of us?

#90-day mentoring challenge.

As the content got rolling out, people started doing the exercises.

It’s great to see everyone making progress.

I am late starting the things as I am trying other things.

But it was great to see everyone around making progress.

What do you learn?

How to communicate with others.

Improve your communication skills. This includes writing and speaking.

The quote on Buffet inspired me.

You learn consulting skills.

How to use Design thinking at work and conduct workshops.

UI and UX, AI.

My favorite module. Personal Branding.

You can see the curriculum here for more details. Mark explained better than me :)

https://ako.nz365guy.com/

Books

You will get many book recommendations from the program that Mark has read every year.

Also from the community.

You can progress professionally and personally if you read and apply a few of them.

My favorite book from the list is Radical Candor by Kim Scott.

What’s more, you can learn?

Having direct access to Mark. This is a game-changer for this program.

QA Sessions

This is the best part for me and many others who always look forward to connecting with Mark and everyone else in the cohort.

Listening to the questions people ask and learning from others.

Mark also encourages everyone to share their thoughts and he adds value.

The good thing is that you get access to all the QA sessions to learn from others.

You might face similar challenges to those others are facing.

These sessions also get recorded, so you can refer to them later.

What I have done since joining the 90-day challenge

Started writing on LinkedIn.

Started answering questions in forums.

I also started learning Power Pages.

Now, blogging.

I will be doing a speaking engagement next month (April 2024) in Athe NZ CoE user group.

What else?

Did a Podcast with Mark.

I am planning to do things for the next three months in advance, which is something you will learn as part of the program.

Why You Should Join

There are many reasons why you should join.

• Making Friends across the globe.

• Supporting each other.

• You can ask questions and learn from experts.

• You get inspired by other people.

• It is a safe place to share stories, emotions, and frustrations.

• Actionable content that solves real-world challenges.

• Everyone is happy for others to succeed.

• Honest conversations and no BS.

• Connections that will last forever.

• This is an opportunity to ask questions and get insights from many people with a range of experiences at work and in life.

And so much more.

Final Thoughts

The 90-day mentoring challenge could be a life-changing opportunity.

You collaborate, make connections, make friends, and grow with others.

I got so much value from the program and the people who are part of the program.

Thank you, Mark https://www.linkedin.com/in/nz365guy/

If you are considering joining, this post might help you decide.

Leave a comment if you have a question about the mentoring challenge. I am happy to answer or redirect the question to Meg and Mark :)

Quarterly goals, however, are underrated. With less than 90 days left in this year 2025, you still have ample time to achieve what you’ve planned. If you’ve already accomplished your goals for the year, great! Take a moment to relax and enjoy the next few months. If not, consider focusing on a 90-day plan to finish strong.

Think like companies do. They set quarterly goals, and so can you.

Use the next 90 days (October, November, and December) to achieve something meaningful to yourself. Whether it’s investing, building a solution, joining a gym, improving your diet, strengthening relationships, or saving for a trip, identify what matters most and work toward it.

Agile Approach

One common obstacle is trying to achieve too many things at once. When planning for 90 days, focus on core areas: relationships, health, work, and money. Pick one priority in each area and start small. Adjust as needed. If you try to tackle too much, you risk accomplishing nothing and losing motivation for future planning.

If you are in the IT world, you know what I am saying.

Identify three key tasks in each area, rank them, and focus on the top one. Only move to the next task once the first is complete. Everything else goes to the backlog. This method ensures steady progress.

Tools can help. Use Excel, Azure DevOps, Trello, Monday, or any other tool to track your tasks, backlog, and completed items.

Choose one thing, stick with it and you will make progress.

Newport, Cal. Slow Productivity: The Lost Art of Accomplishment Without Burnout

Share your goals with an accountability partner. Whether it’s a friend, colleague, or family member, let them know your plans and ask them to check in with you every four weeks. This accountability can keep you on track.

You can also use the Time blocking technique for each task and it works well.

My Plan for 90 days

For me, the next 90 days will be about revisiting the fundamentals of delivering solutions to my customers. With AI evolving rapidly, I want to identify gaps and find ways to deliver solutions more securely, efficiently, and with greater value.

Below is the list of things I am planning to do over the next 90 days. These are no in any particular order.

• 10 minutes of weight lifting once a day

• 1x 2 KM run per week

  In my 40s, I need to work out enough to keep myself healthy

• Weekend time with Priya and the Kids

  Time with Family is more important to me than anything else.

• Mentor 2 to 3 People

  Guiding people who think I can help is important to me, and I would like to make a difference. And who doesn’t want to make a difference in others’ lives?

  I also joined the 90 Day mentoring challenge this year, but this time, I am trying to contribute as a mentor.

• Enable Copilot Studio and Complete Power Automate Desktop Migration

  At work, our team is working on enabling Copilot Studio and UiPath to Power Automate Migration.

• 1 Blog post per week

  This helps in publishing 12 blog posts by the end of this year

Conclusion

Finally, assess your current standing in health, relationships, work, and money. Rate each area from 1 to 10 (10 being the highest) and focus on where you’re underperforming. Remember, this is a long-term game. Continuous effort in these areas will lead to compounding benefits over time.

Start small, stay focused, and make the next 90 days count!

What about you? What is your plan to end 2025 on a high note? Share with me in the comments.

How Time Blocking Works

Time blocking involves dedicating specific time slots in your calendar to focus on particular tasks. For instance, if I had a project to work on, I would block out time in my calendar to ensure I wasn’t pulled into meetings or other distractions unless something urgent came up. This allowed me to prepare throughout the week and ensure timely delivery. By focusing on one task at a time, I was able to provide more accurate timelines to the business, which helped in managing expectations and delivering results by the end of the week.

The Challenges Before Time Blocking

Before adopting time blocking, I found myself constantly juggling multiple requests, jumping from one task to another without making significant progress on any. This approach led to inefficiency and frustration.

Time blocking helped me regain control by ensuring that I wasn’t always available for calls or meetings. This allowed me to focus on building solutions without interruptions, reducing chaos, and increasing productivity.

Handling Urgent Requests

Urgent requests are inevitable in any project. To manage these effectively, I would list all the tasks I was working on and, when a new urgent request came in, I would consult my manager to prioritize. I would ask, “Which task should I focus on, and which one should I drop?” This approach ensured clear communication with my manager and helped me avoid burnout. It also built trust with both my team and customers, as they knew exactly when to expect deliverables.

Final Thoughts

Time blocking is a powerful technique that can transform the way you manage projects. By dedicating specific time slots to focused work, you can increase productivity, manage expectations, and reduce stress.

It’s a strategy that has worked exceptionally well for me, and I highly recommend it to anyone looking to improve their project management skills.

Do you block time to get things done? I am curious to know what works or doesn’t work for you.

Specialists get stuck when the stack shifts. Being “only a Power Platform Developer” or “only a Microsoft 365 Developer” can limit your opportunities.

You need to know fundamentals across M365, Azure, Power Platform, and Dynamics 365, then choose one platform to go deep into where you have the demand. Using this approach, you become more valuable, resilient to platform changes, and better at solution design and trade-offs.

This is the first part of the series, and I will be sending the other parts of the series that you should know before developing your Agent.

1. Master These SharePoint Fundamentals First (This post)

2. Ship Fast, Govern Well: Power Platform Fundamentals + ALM

3. From Process to Product: Dynamics 365 101

4. Azure Basics: Compute, Data, Network, and Security

I started working in SharePoint (Aka MOSS 2007) in 2008/09. There were many changes/updates to the SharePoint product from the beginning. You got upgrades from MOSS 2007 to SharePoint 2010, then from SharePoint 2010 to SharePoint 2013. Later upgraded to SharePoint 2016. While all these things were happening, SharePoint Online slowly gained attention when Microsoft migrated a lot of customers to the cloud.

I worked as a “Microsoft Velocity Manager“ on some of the largest projects initiated by Microsoft to bring customers from on-premises to the cloud. Since then, there have been many changes to SharePoint Online, and it has become so large that now it is one of the main pillars of Microsoft 365 (Aka Office 365). Every agent that Microsoft releases nowadays is based on the foundations built many years ago.

A few things fundamentally stayed the same across all these years with SharePoint. And it’s in DNA.

If you are trying to learn how to build Agents rather than solving business problems, you should know these fundamentals of SharePoint.

Morgan Housel. Same as Ever: Timeless Lessons on Risk, Opportunity and Living a Good Life

Organizations are rushing to build AI agents without understanding the underlying SharePoint DNA that powers them. Without these fundamentals, your agents will fail security audits, break governance models, and create data chaos instead of business value.

They focus on the shiny new AI features instead of mastering the unchanging foundations. They build agents on weak data structures, ignore permission models, and skip metadata strategy - then wonder why their agents can't scale or meet compliance requirements.

Every SharePoint agent is built on foundations laid down 17+ years ago.

1. Collaboration

What it is: Tools and features that enable teams to work together effectively

Key capabilities:

• Comments - Contextual discussions directly on documents and pages

• @mentions - Tag specific people to draw attention and trigger notifications

• Mobile access - Full functionality on smartphones and tablets

Business impact: Breaks down silos, accelerates decision-making, and supports hybrid work environments.

2. Sites

What it is: Digital workspaces that organize content and tools around business purposes

Key capabilities:

• Site hierarchy - Parent and child sites mirror organizational structure

• Navigation - Consistent menu structure across related sites

• Site templates - Pre-built configurations for common scenarios (team sites, communication sites)

• Hub sites - Connect related sites for unified branding and navigation

Business impact: Creates organized digital workplaces that match how your business operates.

3. Document Libraries

What it is: Your digital filing system that replaces network folders

Key capabilities:

• Version control - Every edit creates a new version, so you can restore previous versions

• Check-out system - Lock files while editing to prevent conflicts with other users

• Metadata columns - Add custom properties like project name, status, or department

• Views - Create filtered displays showing only documents that meet specific criteria

Business impact: Eliminates version confusion, reduces email attachments, and provides audit trails for compliance.

4. Lists

What it is: Structured data storage that works like enhanced spreadsheets

Key capabilities:

• Custom columns - Text, numbers, dates, dropdowns, people picker, and more

• Data validation - Enforce business rules and data quality

• Calculated fields - Automatically compute values based on other columns

• Forms - Custom input forms for data entry

Business impact: Centralizes business data, reduces spreadsheet sprawl, and enables better data governance.

5. Metadata

What it is: Descriptive information about your content that makes it discoverable and manageable

Key capabilities:

• Content types - Templates defining what metadata applies to different document types

• Managed metadata - Enterprise-wide taxonomies and tag hierarchies

• Required fields - Enforce metadata entry for better content organization

• Automatic tagging - AI-powered suggestions for consistent tagging

Business impact: Transforms content from hard-to-find files into discoverable business assets.

6. Permissions

What it is: A Security system controlling access to content and functionality

Key capabilities:

• Inheritance - Child items inherit permissions from parent containers

• Unique permissions - Break inheritance for sensitive content

• SharePoint groups - Manage permissions for multiple users at once

• External sharing - Securely share with customers, vendors, or partners

Business impact: Protects sensitive information while enabling collaboration across organizational boundaries.

7. Search

What it is: An Enterprise search engine that finds content across your entire Microsoft 365 environment

Key capabilities:

• Security-trimmed results - Only shows content you have permission to see

• Refinement filters - Narrow results by file type, author, date, or custom metadata

• Search scopes - Limit searches to specific sites or libraries

• Query suggestions - Predictive search based on content and user behavior

Business impact: Reduces time spent hunting for information and increases content utilization.

8. Integration with Microsoft 365

What it is: Seamless connection between SharePoint and Office applications

Key capabilities:

• Co-authoring - Multiple users edit documents simultaneously with real-time updates

• Office Online - Edit documents in a web browser without desktop applications

• Sync - Local copies stay synchronized with SharePoint versions

• Teams integration - SharePoint provides a file storage backbone for Microsoft Teams

Business impact: Eliminates productivity friction and supports modern collaborative work styles.

9. Workflows

What it is: Automated business processes that route content and trigger actions

Key capabilities:

• Approval processes - Route documents through review and approval chains

• Power Automate integration - Connect SharePoint to hundreds of other business applications

• Conditional logic - Different actions based on content properties or user roles

• Notifications - Automatic emails and alerts when process steps are complete

Business impact: Reduces manual tasks, ensures process consistency, and speeds business operations.

10. Web Parts

What it is: Modular components that add functionality to SharePoint pages without coding

Key capabilities:

• News web part - Display announcements and updates with rich formatting

• Document library views - Show filtered document sets on any page

• Calendar integration - Display Outlook calendars and schedule information

• Third-party web parts - Extend functionality with solutions from Microsoft partners

Business impact: Creates engaging intranet pages and dashboards that serve real business needs.

Final Thoughts

There will always be more changes to SharePoint going forward, and it would only speed up with AI tools available. But the fundamentals won't change - they're the bedrock every successful agent implementation stands on.

Before you build your next agent, ask yourself: Are my lists structured properly? Is my metadata strategy solid? Do my permissions make sense? Are my sites organized for scale?

Get these foundations wrong, and no amount of AI wizardry will save your project.

Get them right, and your agents will be the ones who actually deliver business value while others struggle with governance nightmares.

The organizations winning with AI agents aren't the ones with the fanciest demos - they're the ones who never forgot these SharePoint fundamentals.

Did I miss any other core SharePoint feature that you think should be added to the list? What’s one thing that didn’t change for you, and why it’s important?

What’s the one thing that matters most to me?

When we find our “One Thing,” we unlock a compass for living with fewer regrets and more clarity.

• You’ll make decisions that align with your values instead of chasing every opportunity.

• You’ll be less likely to look back with regret.

• You’ll learn the discipline of delayed gratification.

• You’ll start playing the long-term game with the right people.

Many of the best things in life, whether it’s relationships, health, or career, become easier to navigate once we know the One Thing that anchors us.

Most people never take the time to find it. We get caught up in short-term wins, distractions, and other people’s expectations. We chase too many goals and end up scattered, not focused.

Finding your One Thing requires courage, honesty, and some soul-searching.

Ask yourself:

“What’s the one thing that if I do it, I will die without regrets?”

It’s not an easy question. For me, it took weeks, closer to months of reflection. Don’t rush. The answer will reveal itself over time.

If you want help on this journey, the book The One Thing by Gary Keller and Jay Papasan is a great starting point.

Work backward from your One Thing

Once you’ve found it, break it down into actions that align your life today with your long-term vision:

• 10 years / 5 years

  What must I do to stay aligned with my One Thing?

• 36 months

  What progress do I need to see?

• 12 months

  What milestone should I hit?

• 6 months

  What foundation do I need to build?

• 1 month

  What’s one step I can take?

• This week/today

  What’s the single action that moves me forward?

Example: You wanted time freedom and not to worry about finances

• In 10 years / 5 years

  You want your investments to generate regular income that replaces your salary, or at least you can work on a part-time job ( 3 days a week).

• 36 months

  You are saving regularly and investing such that you already see that the goal of Time Freedom is possible.

• 12 months

  If you are saving, let’s say 10%, can you save 20% or earn more to save more? To earn more, what skills do you need to learn?

• 6 months

  Early in your career, your skills will earn more, so you can save more. Identify skills that are in demand and learn so you can increase your salary, such that you can save, invest.

• This week/today

  Based on a 6-month goal, you need to have a weekly plan for what skills you need to learn and how much time you can dedicate.

You can apply this strategy to your Relationships, Health, work, and so on.

This method shifts your daily decisions from reactive to intentional.

Knowing your One Thing helps you become:

• A healthier person

• A better partner or friend

• A more focused professional

• Someone who spends their time on what truly matters

If you already feel happy and fulfilled, you may not need to define your One Thing right now. But if you feel scattered or uncertain, investing time in this exercise can change the trajectory of your life.

Final Thoughts

When I first came across “The One Thing”, it brought clarity on what I wanted to do in my life. Sometimes, you don’t find your one thing immediately, and that’s okay. Give yourself time, keep reflecting on what is happening in your life. You will find your onething. If you have already done this exercise before, let me know in the comments on your experience.

What’s your One Thing? Have you thought about it before?

Take SharePoint as an example. Over the years, we’ve evolved from Farm solutions, sandbox solutions, Add-Ins, SharePoint Framework, Agents, and so on. Similarly, tools like InfoPath and SharePoint Designer workflows have given way to modern solutions, such as AI and automation. The same applies to the Power Platform (oh, now rebranded as Agent Platform).

A decade ago, building an IT Solution was costly and time-consuming. Today, solutions can be delivered in weeks at a fraction of the cost.

Rather than predicting where technology will be in two, five, or ten years, focus on being nimble and proactive. Return to fundamentals often; they are the foundation for growth and opportunity. For instance, adopting a data-driven approach or viewing technology as an enabler can significantly enhance your problem-solving capabilities.

Whether you’re working with SharePoint, Power Platform, Dynamics 365, or Azure, start with the basics. In SharePoint, this means understanding lists and libraries, while in Power Platform, it’s about mastering Dataverse. Azure offers tools like Azure Storage and Azure SQL. Begin with data and ask fundamental questions about its purpose, security, and classification.

The software development lifecycle (SDLC) remains a cornerstone of delivery. Gathering and validating requirements to build, testing, and deploying solutions. The process has remained consistent over the years. While automation and AI have introduced efficiencies, the core stages of SDLC remain unchanged.

• Requirements

• Design

• Development

• Testing

• Deployment

• and support

Focus on these fundamentals to deliver robust solutions.

Process First Approach

One critical yet often overlooked aspect is fixing processes before applying technology. If the process is flawed, no amount of tech will yield the desired outcomes. Engage with business owners to understand their needs, identify areas for improvement, and determine the business value. Only then should you select the appropriate technology to simplify processes, reduce costs, and improve efficiency.

What Problem are you solving?

In SharePoint, Dynamics 365, or Power Platform, data storage and presentation are fundamental. Whether you’re using SharePoint lists for simple data or Dataverse for complex relationships, ask key questions: What problem are you solving? Where is the data currently stored? What are the security, compliance, and retention requirements? Data classification—whether internal, public, confidential, or restricted—plays a vital role in decision-making. Understanding these aspects helps you deliver successful applications.

Final Thoughts

In summary, focus on fundamentals. They are the building blocks that enable you to deliver effective solutions. Whether it’s mastering data concepts, adhering to the SDLC, or fixing processes first, these principles will guide you through the ever-evolving landscape of technology.

How often do you go back to fundamentals to solve problems at work or in life?

Despite being in contract only a few months, I decided to share a few things that might be helpful if you are trying to change from a permanent role to a contract role.

Transitioning from permanent roles to contract roles can seem risky, but it’s also a great opportunity to take on new challenges and work with diverse teams. However, there are key considerations to keep in mind before making the switch.

1. Understand Your Financial Situation

Track your expenses for at least 6-12 months (ideally 24 months) to understand your spending habits.

Build a savings buffer that makes you comfortable—whether it’s 3, 6, or 12 months of expenses. Personally, I aimed for at least 6 months.

2. Seek Advice from Contractors

Talk to people already in contract roles to understand the pros, cons, and rates.

Their firsthand experience can provide invaluable insights.

3. Start with a 6-Month Contract

Begin with a 6-month contract to give yourself a solid runway.

Discuss extension possibilities with your recruiter upfront.

4. Create a 90-Day Plan

Develop a 90-day plan to set yourself up for success in the new role.

Focus on understanding how you can support your team and manager.

5. Build Trust and Deliver Results

As an outsider, you bring fresh perspectives, but avoid suggesting changes too early.

Focus on excelling at assigned tasks to build trust and credibility.

6. Identify Opportunities for Improvement

Log potential improvements from the start and present them incrementally.

This approach can lead to extensions and further opportunities.

7. Address Personal and Professional Concerns

Consider how the transition impacts your finances, family, and long-term goals.

Discuss these concerns openly with your support system.

8. Overcome Initial Challenges

Questions about team support, community, and perceptions from your previous employer are common.

In my case, these concerns were resolved positively, and my former colleagues were supportive of my decision.

Final Thoughts

Contracting offers unique opportunities for growth and flexibility. If you’re considering this path, take the time to plan, seek advice, and approach the transition with confidence. Please don't hesitate to reach out if you have any questions. I’m happy to help!

If you are keen, I also recommend watching videos done by Parvez

Breaking into Contracting: Tips & Trends with Parvez Ghumra (Video)

Contracting Secrets In The Power Platform (Podcast)

If you worked in contracting, what is one thing you would add to the list?

Here is the list of reasons that could help you understand why you should listen to me.

I studied for a diploma in electrical and electronics engineering for six years.

Didn’t know much about computers when I was a kid.

Forget about being a school kid, even in my engineering days.

I was dreaming about machines.

Then,

I started working as a .NET developer, writing C # code.

I started working with MOSS in 2007 and had yet to learn what it was when I started.

I started working at the delivery centers most of the time.

I only started my consulting career once I moved to Perth.

I spent 10 years working at delivery centers and working with large teams.

Okay, a few more to the list before I finish.

I became an MVP in 2015 and will be one until 2019 for 5 consecutive years.

Worked with 100s of business users developing solutions using Power Platform and its related technologies.

Did that help you to listen to me?

Image credit: Think Again by Adam Grant

Although I solved various problems using Microsoft Tech space for a long enough, I do not know many things.

If you see something wrong or incorrect in posts, please use the comments section and let me know.

Why Now?

I have been reflecting a lot these days.

Made heaps of mistakes throughout my journey.

I made some progress and wanted to share the lessons, mistakes, and failures with you.

Hopefully, you can learn from these and may not repeat them.