The Evolution of Care

-

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. This is the core of this blog and my mission for 2026.

What “Care and Low-Code” Looks Like Today

We are currently in a hectic digital era where “more tech” often feels like “more work.” I am here to challenge that.

  • Building with Clinical Eyes. If it wouldn’t work during a chaotic Tuesday shift in a municipal ward, it doesn’t belong in my stack.
  • The Power of Low-Code. Closing the gap between the IT office and the frontline.
  • Radical Cross-functional Collaboration. Making public value a functional requirement.

This Is the Presence of Change

The public sector doesn’t need more digitalization for the sake of it. It needs Care-First Technology.

My name is Sylvia Wangari, and this is Care and Low-Code.


Where do you see the biggest gap between “the system” and “the person” today?
Please share in the comment section. 

Comments

Post a Comment

Popular posts from this blog

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

-
Image
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 whil...
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