# My Portfolio <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-briefcase-business"><path d="M12 12h.01"></path><path d="M16 6V4a2 2 0 0 0-2-2h-4a2 2 0 0 0-2 2v2"></path><path d="M22 13a18.15 18.15 0 0 1-20 0"></path><rect width="20" height="14" x="2" y="6" rx="2"></rect></svg> --- > [!tldr] What I'm building > A space that helps people reflect & reclaim their relationship with digital tools and data; moving from dependency and extraction toward sovereignty and genuine capability. > [!info]- > This is my professional portfolio - if you're interested in working with me, my organization-agnostic case studies, or learning more about the "business" of [[Cognitive Architecture]] you've come to the right place. For a more personal look [[About me|click here]]. > [!help] Questions? > Get in touch! > [email protected] > > [!link] #### Links [LinkedIn](https://www.linkedin.com/in/sebastian-l-8b6688225/) [GitHub](https://github.com/Seb-the-Canadian) ## Field Notes <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-notebook-pen"><path d="M13.4 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2v-7.4"></path><path d="M2 6h4"></path><path d="M2 10h4"></path><path d="M2 14h4"></path><path d="M2 18h4"></path><path d="M21.378 5.626a1 1 0 1 0-3.004-3.004l-5.01 5.012a2 2 0 0 0-.506.854l-.837 2.87a.5.5 0 0 0 .62.62l2.87-.837a2 2 0 0 0 .854-.506z"></path></svg> --- *These are notes created from my observations working day today. They reflect my thinking and some of my approaches from a "pedagogy" standpoint.* [[Beyond the binary - data fluency over data literacy.]] [[Default Decisions - LinkedIn's 2025 AI Policy Update]] [[When Hesitation is Data - Rethinking AI Adoption Competency]] ## More about My Professional Practice --- I'm interested in how people and organizations build the capacity to navigate digital change wisely—not just adopt new tools, but develop the clarity and infrastructure to think through what these technologies mean for how they work, decide, and create value. My thinking draws on systems analysis, adult learning principles, and philosophical inquiry to examine questions that surface when digital tools move from exciting possibility to daily reality. I don't assume digital adoption is inherently good, or that resistance signals a problem. I'm interested in what you're actually optimizing for, the tensions between efficiency and agency, and how to build change practices grounded in how people genuinely learn—not how we wish they would. My background brings together enterprise learning design, organizational change facilitation, and academic grounding in sociology and systems thinking. I've spent 7+ years inside digital transformation efforts at scale, but I'm increasingly interested in how these insights apply to individuals and smaller organizations—contexts where you can't outsource thinking to a strategy team or wait for enterprise-level solutions. ## Why You Might want to Work with Me <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-users"><path d="M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2"></path><path d="M16 3.128a4 4 0 0 1 0 7.744"></path><path d="M22 21v-2a4 4 0 0 0-3-3.87"></path><circle cx="9" cy="7" r="4"></circle></svg> --- Most approaches to digital transformation focus on implementation: which tools to use, how to train people, how to measure adoption. I'm trying to build foundations on a deeper level; the cognitive and cultural infrastructure that determines whether digital change actually serves your goals—or just creates sophisticated ways to do the wrong things faster. The question isn't just "which AI tool should I use" or "how do I implement this platform"—it's "how do I build digital and data infrastructure that preserves my agency, serves my actual goals, and doesn't lock me into systems designed to extract value while limiting my autonomy?" My focus is on: - Data fluency that enables clear thinking about what information matters and why - Low-friction approaches to digital infrastructure that prioritize portability over vendor lock-in - Sustainable practices for working with emerging tools without surrendering control - Frameworks for thinking about data sovereignty in practical, implementable terms Regardless of your day-to-day, the core challenge is similar: how do you adopt digital capability in ways that enhance rather than erode your autonomy? If you're committed to building digital and data practices that work for you - not just adopting whatever's trending or accepting platform dependency as inevitable - I'd welcome the conversation. I'm looking to learn from people navigating these tensions across different contexts, especially those willing to question conventional wisdom about how digital transformation "should" work.