From Social Work to Microsoft Consultant Associate: Governing the Process of a Career Pivot.

-

On 17 January 2026, I passed PL‑200!


This desk. Same spot. Same time. Same drink. Every single day.

Pink sticky notes = my daily minimums. Laptop = 45 minutes of focused work. No exceptions.


Coming from social work, my job has always been to design systems that still work when people are tired, stressed, or having a bad day, so I applied that same mindset to learning.  

Instead of relying on willpower, I built a system around my motivation, which let me catch mistakes before they snowballed.

The core idea: Govern the process, not just the output.


Step 1: make discipline measurable (SMART)


I didn’t set a vague goal like “study more.” I needed structure and hands-on experience, so I joined the Microsoft Power Up Program (Cohort 28, Fall 2025), a free program designed to help people build practical skills through guided, hands-on learning.


For three months, I deep-dived into Power Apps with one clear outcome: build an end-to-end Smart Parking & Permit Management solution while studying PL‑200 topics through daily practice and weekly builds.


I treated my study plan like a SMART goal: Specific, Measurable, Achievable, Relevant, Time-bound. That turned discipline into a scoreboard, not a personality trait.

​


Step 2: remove friction with ABC behavior analysis

  • Antecedent: I came home mentally tired.
  • Behavior: “I’ll start later” turned into avoidance.
  • Consequence: guilt, inconsistency, and slower progress.

Same desk. Same spot. Same drink (AM and PM). Same time. Every single day.

Pink sticky notes = my daily minimums. Laptop = 45 minutes of focused work. No exceptions.

Step 3: plan intensity around cognitive load (cycle syncing)

Instead of blaming myself for procrastinating, I mapped the pattern using the ABC model: Antecedent → Behavior → Consequence.



So I stopped trying to “want it more” and changed the antecedent. I made starting automatic (open notes the moment I sat down) and removed decisions that drained my remaining energy.


Takeaway: success isn’t only willpower, design your environment so good habits are easier to trigger.



Step 4: build a “bad‑day minimum” (consistency survives)


I didn’t fight my biology, I planned around it.


I mapped harder topics (like Dataverse architecture) to higher-energy days and used lower-energy days for follow-along builds and review. That mattered because cognitive load is real: when working memory is overloaded, learning slows and frustration rises.

​


My rule: if it only works on my best day, it’s not a system.


So I created a minimum viable day:


1. Key Concept (focus)- Example: Understand Dataverse relationships between tables (Users, Vehicles, Permits).

- Why it matters: your data model determines how your app functions and enforces rules.​


2.Tiny Hands-On Task (implementation)

- Example: Create a “Permit” table in Dataverse with columns: PermitID, User, Vehicle, Status, ExpiryDate.
- Add lookup columns to link Permit → User and Permit → Vehicle (this creates the relationships).​
- Keep it small: no flows, no forms—just the table and relationships.


3. Quick Check (reinforce)
- Verify in Dataverse: Can one user have multiple permits?
- Can a permit be linked to one vehicle?​
- Mini-quiz: “Which relationship type supports one user → many permits?” (Answer: 1:N / N:1 depending on viewpoint).​
- Optional: write 1 sentence on why this relationship matters for permit management.



Step 5: the 80% confidence rule


In care work, you don’t make high-stakes decisions without enough certainty (assumptions kill- both literally and figuratively).


I used that same principle for exam readiness: I didn’t book the exam until my results were consistently strong and repeatable, not just “one lucky attempt.”


Step 6: ambient integration (make life the classroom)

I stopped relying on long “perfect” sessions.


Instead, I did short, intense morning sessions, used Pomodoro-style focus, and added “treadmill learning” for review. Learning became part of my environment, not something separate from my life.


That’s what made consistency possible with a full-time job.


Step 6: Accountability & Community

No system survives in isolation. Pair your daily routine with people who keep you consistent.

  • Accountability partner: 1 check-in weekly/or when in need of a push (wins, blockers, next step).

  • Mentor: someone ahead of you who can review your builds and help you avoid common pitfalls.

  • Community: ask questions, share progress and lessons (eg LinkedIn Carousels or blogpost or even Youtube and get unstuck fast.

This was the missing layer for me: structure + community turned motivation into a system I could trust.


Closing

Passing PL‑200 wasn’t just a technical milestone. It proved the Care‑First approach works: define the goal clearly, design around human limits, and build a system that survives bad days.


If you’re transitioning into tech (or studying PL‑200), what’s your biggest blocker right now: time, confidence, or knowing what to study and do you have a system? 



Follow and subscribe to Care & Lowcode for daily tips and practical insights on transitioning into a tech career and building better low-code solutions. Youtube@careandlowcode


Resources (Free)

Official PL‑200 + practice

Hands-on learning program

Dataverse (for the “bad‑day minimum” example)

Community (ask questions, get unstuck)

Governance / admin (high-value for PL‑200)




Comments

Post a Comment

Popular posts from this blog

The Evolution of Care

-
Image
Why I Am Building for the Frontline. As a Social Educator, I work at the intersection of municipal health, specialist services, and welfare. I see firsthand where systems break down, where data stops flowing, and where the human impact is greatest. My focus is on bridging these gaps to create insights and solutions that truly work for people. Care is not a static act. It must evolve. If my ten years in the field taught me what needs to happen, my transition into the tech world over the last six months has taught me how to make it happen at scale. Care Is Evolving - And So Am I I used to think that care only happened in a living room or a clinic. I was wrong. Care is also found in the code that ensures a patient’s history is available when it’s needed most. Care is found in the low-code interface that saves a nurse thirty minutes of redundant data entry. I am not leaving care; I am evolving into a new form of it. I am moving from direct care to systemic care . Thi...
Read more

Hierarchy Security in Dataverse

-
Image
Unlocking Hierarchy Security in Dataverse . 3-minute read | Power up journey|PL-200 Study Notes I’ve recently gained my Dataverse explorer badge from Power Up Program, and I wanted to share a specific feature that stood out to me: Hierarchy Security . It’s a documented way to solve a very common problem how to give managers visibility into their team's data without over-complicating security roles. Here is the traceable theory I’ve gathered from Microsoft Learn.  The Core Theory: Beyond Basic Roles In Dataverse, we usually think of security in terms of Security Roles (which define what actions you can take, like Read or Delete).  Hierarchy security is a documented additive layer that defines which records you can see based on your place in the organizational structure.   Verification:   It does not o verride Roles: You still need a Security Role with "Read" access to the table.   The Two Documented Models According to Microsoft documentation, there are two ...
Read more