a reflection on the last 2 months 📆:
🧑🏻💻 SLS: designed for learning 🧑🏻🎨
edtech is not synonymous to device use!!!
SLS as a means to preserve pedagogy
productivity tool vs learning system
productivity tool - increases dependency; addictive; people are unlikely to wean off the tool
introduction of gen AI complicates things – not just a productivity tool, but also a cognitive tool, creativity tool, etc. ➡️ dependency!!!
SLS may not be the best learning system, but it is designed for learning; not a productivity tool
deliberate friction for students
importance of INTENTIONAL use of tech
at some point, the tool needs to be “switched off” to test mastery; tools that can add friction
e.g. GPS, smart hotel
🧠 initial brain tangles 🪢
conflating SLS as an infrastructure and SLS as a means to actualise e-Pedagogy
what i'm familiar with = the latter
🌱 now equipping myself with the vocab to promote SLS as OSH
seeing where/how my work pieces fit in into the larger puzzle
especially when i'm working on something that's already 85% done (e.g. OSH action plan school consultation)
🌱 ask more questions! (importantly, ask the right questions)
intent? target audience? desired outcomes?
alignment with bigger picture (organisational/ministry outcomes)
🤝🏻 on working relationships ⚖️
with vendors: being clear about our roles; not taking over or doing others' work just because theirs isn’t up to standard
help them to level up (to a reasonable extent)
trust? e.g. do we continue to do further testing after vendor has provided their input re: root cause of ops issue?
tension between due diligence (for cases we can verify) and leaning on vendor's assessment (for more technical cases)
though at the end of the day it is not possible/logical for us to try to replicate every single issue ➡️ be strategic about raising such issues/letting the other party know you are monitoring? e.g. production UAT review
ultimately, we own SLS and are therefore responsible for fronting it
others don't see ufin/3rd-party vendors
📢 marcomms learnings 👩🏻🏫
intentionality !!
every single small thing needs to be considered (think butterfly effect 🦋)
e.g. OSH checklist
quantitative vs. qualitative: purely quantitative ➡️ could this possibly encourage/drive “undesirable’ behaviour — i.e. jumping into hitting percentages instead of achieving economies of scale
how to measure things like extent of synergy?
📊 operations learnings 💻
be proactive not reactive (service design)
look for root cause and solve it before it balloons ➡️ see possible connections to other similar issues, aggregate common areas where user still face issues/processes that are unsmooth ➡️ propose ways to optimise process/workflow
but also, always seek context of existing processes / why certain decisions were made
precedence? broader norms?
💭 for future wenxin to look back on 🥛
discomfort = growth !! 😊
something i'm looking forward to: not being stressed x1000 every time I schedule a meeting/send an email 🤣
Comments