# organizations Published articles for organizations. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## TBM 434: How Maps Can Hide Problems DevFeed: [TBM 434: How Maps Can Hide Problems]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-08-01T09:13:07Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [context](), [structure]() Tags: [design](), [mapping](), [maps](), [organizations](), [ownership](), [problems](), [product](), [reporting](), [silos](), [structure](), [technology]() ### AI overview The article argues that organizational maps can conceal incoherence when strategy, structure, technology, incentives, goals, ownership, teams, and funding do not align. It contrasts coherent organizations, where context transfers across map layers, with incoherent organizations, where people must repeatedly reorient and translate. ### Source excerpt If what you are mapping is incoherent, don't fall in love with the map (or your personal ability to navigate with it). ## How MIT students are helping to prevent cyberattacks DevFeed: [How MIT students are helping to prevent cyberattacks]() Original publisher: [Read original article]() Author: Nicole Estvanik Taylor | Department of Urban Studies and Planning Published: 2026-07-13T19:10:00Z Content type: article Language: en Sources: [MIT AI News]() Topics: [Cybersecurity](), [Security & Privacy](), [ransomware](), [Business Security]() Tags: [ai-and-security](), [ai-in-cyber-crime](), [artificial-intelligence](), [attacks](), [business-and-management](), [classes-and-programs](), [collaboration](), [computer-science-and-technology](), [cyber-attacks](), [cybersecurity](), [government](), [health-care](), [jungwoo-chun](), [lawrence-susskind](), [local](), [massive-open-online-courses-moocs](), [mit-class-11-074-11-274-cybersecurity-clinic](), [mit-cybersecurity-clinic](), [mit-dusp](), [mitx](), [organizations](), [prevent](), [public-sector](), [ransomware-attacks](), [school-of-architecture-and-planning](), [software](), [technology-and-society](), [training](), [urban-studies-and-planning](), [vulnerabilities]() ### AI overview MIT's Cybersecurity Clinic trains students to assess cyberattack vulnerabilities and provide free, confidential security assessments to municipalities, health-care organizations, and other at-risk communities. ### Source excerpt Students from the MIT Cybersecurity Clinic help local governments and other vulnerable organizations defend against digital threats. ## Making Sense of Digital Transformation Initiatives: Seeing Past the Fuzziness DevFeed: [Making Sense of Digital Transformation Initiatives: Seeing Past the Fuzziness]() Original publisher: [Read original article]() Author: Josh Korr Published: 2026-02-13T23:41:00Z Content type: article Language: en Sources: [8th Light Insights]() Topics: [digital](), [product mindset](), [Optimization]() Tags: [digital-transformation](), [optimization](), [organizations](), [product](), [product-strategy-innovation](), [project](), [strategy](), [structured](), [transformation]() ### AI overview This article explains why digital transformation initiatives often become unclear in practice and argues that short, structured strategy and shaping phases can create shared clarity. It discusses how these initiatives may involve business-model shifts, cultural change, product thinking, and process optimization, illustrated by client examples. ### Source excerpt Digital transformation always sounds clear in an RFP or slide deck, but in practice things can get fuzzy fast. What exactly are we transforming? Is this about customers, or about ourselves? Are we reshaping workflows, or the entire business model? Without answers to these questions, projects stall, swirl, or never quite get started in the first place. As a Certified Sense-MakerTM and fuzziness connoisseur, I love helping clients make sense of their digital transformation initiatives.* This includes helping them understand the bigger picture, what their plans will mean for business operations, and what tools or solutions can help. By implementing short, structured strategy and shaping phases, organizations can gain shared clarity and overcome transformational fuzziness. * Just kidding: there isn't a Sense-Maker(tm) certification. (Sigh.) Fuzziness Factor #1: The Big Picture Digital transformation initiatives are typically triggered by something bigger: business model shifts or expansions, operational maturation, rebrands or relaunches. And these initiatives go far beyond technology upgrades. There is a very real shift in culture, a move towards a product mindset, and an optimization of processes that meet the demands of the market. When done well, these initiatives have a lasting impact on the organization and the benefits show up on the bottom line. But teams that are at the "ground level" of this transformative work often have a fuzzy understanding of the macro-strategy and how the immediate near-term effort fits in. Take a Fortune 500 media company I worked with. They had debated for a year whether to introduce self-serve sales alongside their high-touch direct sales model. Nothing with the project had moved because no one had named the real issue: This wasn't just a sales project -- it was a business model transformation. Misalignment across stakeholders was causing them to delay decisions. Once reframed as a fundamental cultural and business model shift, two thin ## Demonstrably Secure Software Supply Chains with Nix DevFeed: [Demonstrably Secure Software Supply Chains with Nix]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2025-05-12T00:00:00Z Content type: article Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [supply-chain-security](), [open-source-security](), [integrity](), [Security](), [toolchains](), [audit]() Tags: [audit](), [audits](), [builds](), [capabilities](), [compilers](), [compliance](), [environments](), [government](), [integrity](), [local](), [offline](), [organizations](), [rebuilds](), [secure-software](), [security](), [software](), [software-supply-chain](), [software-supply-chain-security](), [supply-chain](), [supply-chain-security]() ### AI overview This article explains how Nix can support verifiable software supply chain integrity. It describes tracing sources and toolchains, enabling hermetic offline rebuilds, and exporting release sources for audits to help meet regulatory requirements. ### Source excerpt Discover how Nix can revolutionize your software supply chain security, enabling verifiable integrity and offline rebuilds from source. ## Organizational Tension Processing - Driving Change in Self-Organizing Companies DevFeed: [Organizational Tension Processing - Driving Change in Self-Organizing Companies]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-10-05T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [structure](), [Processes]() Tags: [business-culture-employee-happiness-high-purpose-environments-leadership-developer-productivity](), [change](), [hierarchy](), [organizational](), [organizations](), [processes](), [product-development](), [self-organizing](), [structure]() ### AI overview The article explains that self-organizing companies are not structureless or chaotic despite having no traditional people hierarchy. It discusses using a tension-based proposal process to adjust structures, processes, and goals while enabling employees to surface and implement ideas and support faster organizational change. ### Source excerpt Organizational Tension Processing - Driving Change in Self-Organizing Companies Newcomers to self-organization often mistake the lack of a people-hierarchy for complete chaos. The term "flat" can be misleading, as it suggests that self-organizing companies lack any structure. In reality, this is far from the case. ## Exploring Temporal Cloud automation features DevFeed: [Exploring Temporal Cloud automation features]() Original publisher: [Read original article]() Author: Irina Belova Published: 2024-03-25T06:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Automation](), [Cloud](), [terraform provider](), [API](), [Infrastructure as code](), [API keys](), [certificates](), [Security](), [Authentication](), [Command-line interface](), [Kubernetes]() Tags: [api](), [api-keys](), [automation](), [certificates](), [cli](), [cloud](), [infrastructure-as-code](), [mtls](), [organizations](), [platform-teams](), [provisioning](), [security](), [temporal](), [temporal-concepts](), [terraform-provider]() ### AI overview Temporal Cloud's automation features support management of namespaces, users, access, account settings, and team onboarding. The article also describes API, Terraform provider, and Temporal Cloud CLI integrations, including automated mTLS certificate rotation and centralized governance for platform teams. ### Source excerpt Temporal Cloud Automation capabilities are transforming the way companies deploy, manage, and scale their operations in the Cloud. ## Deciding Which ICT Tasks to Keep In-House or Outsource DevFeed: [Deciding Which ICT Tasks to Keep In-House or Outsource]() Original publisher: [Read original article]() Published: 2024-03-02T16:30:55Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [service](), [Server](), [amazon](), [cloud-infrastructure]() Tags: [amazon](), [autonomy](), [employees](), [management](), [organizations](), [outsourcing](), [servers](), [service]() ### AI overview This opinion article discusses how organizations decide whether to keep ICT tasks in-house or outsource them. It argues that prolonged indecision can lead to the loss of internal expertise and recommends making deliberate decisions while retaining a smaller core ICT team. ### Source excerpt The short version: organizations often hesitate for many years before outsourcing tasks, particularly in the field of ICT (Information and Communication Technology). During those years, valuable ICT employees leave because constantly justifying their own existence is frustrating. In the long run, something will eventually go wrong, making the decision to outsource much easier: "We can't and don't want to do this ourselves anymore." However, by hesitating for so long, you have created the situation yourself. ## How to sell MLOps in large Organizations DevFeed: [How to sell MLOps in large Organizations]() Original publisher: [Read original article]() Author: Raphaël Hoogvliets Published: 2024-02-07T09:36:58Z Content type: tutorial Language: en Sources: [Raphaël Hoogvliets]() Topics: [MLOps](), [data-governance](), [Security]() Tags: [how-to](), [mlops](), [organizations](), [stakeholder-management](), [strategy]() ### AI overview This article offers practical advice for gaining management buy-in for MLOps initiatives in non-technical organizations where machine learning is still viewed as a nice-to-have. It argues that MLOps is often overlooked despite helping keep data investments and ML results available, dependable, and tested. ### Source excerpt A toolbox for strategy and stakeholder management ## Self-organizing companies don't need managers but coaches DevFeed: [Self-organizing companies don't need managers but coaches]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2024-01-20T05:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Self-organizing Team](), [Agile]() Tags: [agile](), [coaching](), [developer-experience-developer-productivity-engineering-leadership-high-purpose-environments-lea](), [manager](), [motivation](), [organizational-structure](), [organizations](), [self-organizing](), [teams]() ### AI overview The article argues that self-organizing companies need coaching roles beyond traditional management and classic agile coaching. It presents self-organization as a way to improve organizational adaptability and create more impact, enjoyment, and human connection at work. ### Source excerpt Self-organizing companies don't need managers but coaches If you are a manager or consider managing teams and organizations a significant part of your profession, the title will likely cause a feeling of rejection or a strong disagreement. I invite you to read on anyway. ## Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies DevFeed: [Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-10-21T04:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [developer-productivity](), [Development]() Tags: [culture-developer-experience-developer-productivity-engineering-excellence-organizational-design](), [developer-experience](), [developer-productivity](), [development](), [devex](), [organizations]() ### AI overview This opinion article discusses how technical leaders can communicate and advocate for Developer Experience initiatives by aligning them with organizational priorities. It contrasts purpose-oriented and profit-oriented contexts and relates DevEx to developer productivity and effectiveness. ### Source excerpt Selling DevEx Initiatives in Purpose vs. Profit-oriented Companies For years, a conversation has been ongoing on naming in the DevEx community (and within myself). Of course. Naming is hard, and why shouldn't it be any different for this domain? ## The Importance of an Engineering Vision (High-Purpose Environments, Part 2) DevFeed: [The Importance of an Engineering Vision (High-Purpose Environments, Part 2)]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-05-13T05:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Statement]() Tags: [culture-high-purpose-environments-engineering-excellence-organizational-design](), [engineering](), [leader](), [mission](), [organizations](), [strategy](), [teams](), [values](), [vision](), [work]() ### AI overview This article explains how a clear engineering vision, mission, strategy, guiding principles, and values can help teams make progress and support leadership without relying on hierarchy or power. It defines the distinctions among vision, mission, and strategy and presents examples. ### Source excerpt The Importance of an Engineering Vision (High-Purpose Environments, Part 2) Have you ever seen organizations and teams spinning in circles, having endless discussions, and never seeming able to make progress? Have you witnessed environments where every decision was made by a leader in the hierarchical sense? Or even worse, by someone able to exert a specific power and overrule others? ## New Keycloak maintainer: Thomas Darimont DevFeed: [New Keycloak maintainer: Thomas Darimont]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2021-09-17T00:00:00Z Content type: news Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [observability]() Tags: [bug-fixes](), [cloud-native](), [community](), [conferences](), [contributions](), [design](), [germany](), [idm](), [kerberos](), [keycloak](), [ldap](), [maintainers](), [new-features](), [observability](), [openid-connect](), [organizations](), [saml](), [sso]() ### AI overview Keycloak welcomes Thomas Darimont as an official maintainer. He will contribute to the Keycloak.X effort, with an initial focus on observability and cloud-native experience, while also reviewing contributions and participating in community and feature discussions. ### Source excerpt We are extremely pleased to welcome Thomas Darimont as an official maintainer of Keycloak. Thomas has contributed to Keycloak since 2015, and is well known and respected by the current maintainers, as well as the Keycloak community. He has enriched the community through practical examples, valuable discussions on mailing lists, and presenting at conferences. In addition, he has also helped with design discussions, contributed bug fixes, as well as new features. Thomas will start by helping us with our Keycloak.X effort, with first focusing on an excellent observability story for a true cloud native experience. In addition he will help review and sponsor community contributions, engage with the community, and join in discussions around new features and capabilities. We're seeing more and more people getting involved in the Keycloak community, and a lot of continued commitment and contributions from large organizations to Keycloak. Thomas works for codecentric AG in Germany, which sees the real value of Keycloak allowing him to invest a significant portion of his time to the Keycloak project. The Keycloak team is very exited about having Thomas join us as a maintainer, and we are looking forward to working more closely with Thomas going forward. ## Models and Accuracy (Threat Modeling Thursday) DevFeed: [Models and Accuracy (Threat Modeling Thursday)]() Original publisher: [Read original article]() Author: Adam Published: 2020-05-14T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Math and Logic]() Tags: [change](), [covid](), [model](), [models](), [organizations](), [policy](), [quality]() ### AI overview An opinion piece examines model accuracy through COVID models and threat modeling. It argues that models are rarely perfect but can still be useful when they expose choices or impacts and help organizations drive change. ### Source excerpt For Threat Model Thursday, I want to look at models and modeling in a tremendously high-stakes space: COVID models. ## Podcast on Atomic Kotlin and Teal Organizations DevFeed: [Podcast on Atomic Kotlin and Teal Organizations]() Original publisher: [Read original article]() Author: Bruce Eckel Published: 2019-10-14T00:00:00Z Content type: opinion Language: en Sources: [Bruce Eckel - Computing Thoughts]() Topics: [Kotlin](), [Software]() Tags: [kotlin](), [organizations](), [podcast]() ### AI overview The author discusses a Six Figure Developer podcast interview, their appreciation of Kotlin while writing Atomic Kotlin, and an experiment with creating a Teal software consulting firm. ### Source excerpt A recent interview with The Six Figure Developer podcast. I talk about how much I'm enjoying the design of Kotlin while writing Atomic Kotlin and also my experiment with creating a "Teal" software consulting firm. ## India's Intermediary Guidelines DevFeed: [India's Intermediary Guidelines]() Original publisher: [Read original article]() Author: Adam Published: 2019-03-18T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Security](), [Internet](), [information-technology]() Tags: [government](), [india](), [information](), [internet](), [organizations](), [privacy](), [security]() ### AI overview The author says they signed Access Now's letter urging India's Ministry of Electronics and Information Technology to withdraw draft amendments to the Information Technology (Intermediary Guidelines) Rules. The letter argues that the proposed tracing requirement could weaken product and service security and threaten privacy and free expression. ### Source excerpt I've signed on to Access Now's letter to the Indian Ministry of Electronics and Information Technology, asking the Government of India to withdraw the draft amendments proposed to the Information Technology (Intermediary Guidelines) Rules. ## Keeping the Internet Secure DevFeed: [Keeping the Internet Secure]() Original publisher: [Read original article]() Author: Adam Published: 2018-07-17T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Digital Security](), [Encryption](), [Cybersecurity](), [Security]() Tags: [australia](), [cybersecurity](), [digital-security](), [encryption](), [global](), [government](), [law](), [organizations](), [policies](), [security]() ### AI overview A global coalition of civil society and technology experts urged the Australian government to abandon proposed legislation that would require device manufacturers to help law enforcement access encrypted information. The letter argues that weakening encryption would threaten individual rights, economic safety, and security, while calling for collaboration on law-enforcement adaptation to the digital era. ### Source excerpt [no description provided] ## New GitHub Organization API and deppbot DevFeed: [New GitHub Organization API and deppbot]() Original publisher: [Read original article]() Published: 2015-11-26T06:07:48Z Content type: article Language: en Sources: [Jolly Good Code]() Topics: [GitHub](), [API](), [Authorization]() Tags: [api](), [change](), [github](), [organization](), [organizations](), [permissions](), [reduce]() ### AI overview The article reports that deppbot.com was changed to reduce its access permissions on GitHub organizations and repositories. ### Source excerpt About two weeks ago, we made a change to deppbot.com to reduce the access permissions it has on GitHub organizations and their repos. ## Scaling Organizations - Scribing DevFeed: [Scaling Organizations - Scribing]() Original publisher: [Read original article]() Author: Map Published: 2014-07-14T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [scaling](), [meetings](), [Development]() Tags: [context](), [development](), [growth](), [meetings](), [organizations](), [philosophies](), [practical](), [process](), [scaling](), [team]() ### AI overview The article discusses how planning and meeting documentation need to evolve as organizations and development teams grow. It recommends concise but sufficiently detailed planning summaries, running meeting notes, attendance records, and explicitly communicating information to absent team members so context is not lost. ### Source excerpt In the process of growing a company there's several hurdles based on the size of the company. What worked at 5 doesn't work at 20, what works at 20 doesn't work at 50, and what worked at 50 doesn't work at 150. There's a lot of talk about two pizza teams and scaling development teams out there. One thing I haven't seen quite enough of is details around scribing and documenting things. Planning At teams of 2 and 3 you get everyone in a room. Perhaps 1 person says what you're going to do and you all rally around it, or maybe it's a day of debate and persuasion from all sides. In the end though you all leave, get heads down, but all know what goal you're working towards. At a larger company planning doesn't scale quite this way. I've seen roadmapping and planning done a variety of ways as companies scale, but most times the thing they miss for far too long is documenting what comes out of it. Many may produce some level of artifact, but a cohesive wrap-up is often missed. Such an artifact should be easily digestible within a couple minutes, but also deep enough to answer many of the initial questions raised by the high level pieces. Meetings Meetings are a smaller level item than broader planning, and tend to go without thorough note taking than higher level planning. With growth you'll have more meetings, trust me you will. The more meetings you have the more likely you may miss one or two you're interested in. Or perhaps its as simple as some team members being out. Summer is especially hard around this. For a team of 10 it's not uncommon that you may go all summer with at least 1 person not in the meeting and often two. Keeping those that miss the meeting well informed of what happened at it is critical as you scale. This is slightly less important at an extremely large company, though still valuable, but critical as you scale to larger. As you're scaling things are changing faster, and context can more easily get lost. So how do you improve this? Some practical tip