New features for the AirPods are expected to be announced at WWDC next week.

Here are some hints and the answers for Connections for June 7, #727.

A Garmin Index Sleep Monitor video just got leaked by a regional arm of Garmin, then quickly taken down.

FORM Brands Studio has given London’s Air Ambulance Charity a new look. Rather than transporting patients to hospital, the charity’s doctors and paramedics treat seriously injured people at the scene from its two helicopters and eight cars. It is the only organisation performing this role in London. Established in 1989, it is called to a rising number of patients across the capital every year, helping more than 2,000 people in 2024. London’s Air Ambulance Charity (LAAC) needs £17m a year to operate, 96% which comes from donations. “But 60% of Londoners don’t know we’re a charity,” says LAAC’s director of fundraising and marketing, Jayne Clarke. FORM Brands Studio identity for London’s Air Ambulance Charity in OOH posters Its new organisational strategy is about raising awareness, enhancing fundraising efforts and strengthening its connection with London’s communities. “We’re trying to make sure the strategy is about hope and looking forward to the future,” Clarke says. To accompany this new strategy, the charity also decided to change up its visual identity. “Our previous branding was very corporate,” Clarke admits.FORM Brands Studio won the job after a pitch. Strategy director Beth Andlaw set up the east London agency in 2022 with creative director Alex Andlaw. Before that she had been in comms and PR, and had worked with LAAC on and off for about 20 years. FORM Brands Studio identity for London’s Air Ambulance Charity on stage FORM introduced a new wordmark, colour palette, typeface, icons, motion, creative copy, messaging, fundraising memorabilia and photography. However, the existing helicopter icon was retained. “It has a lot of love and legacy,” says Clarke. The agency’s brand idea, Propelling Promise, was inspired by the urgent, intense nature of the work carried out by LAAC’s clinical and operational crews. That was used to give structure to creative copy lines and the new tone of voice. Each lead line includes an element of “propelling” to imply urgency and momentum, and “promise” to imply warmth and hope. That resulted in lines including “Trauma doesn’t stop. Neither do we” and “Here for London. Today, tomorrow, always.” FORM brought in Peggy Nyamekye to work on the copywriting. Meanwhile, the visual identity, developed with designer Mayan Mistry, comprises a gradient design system, drawing on the rotational motion of helicopter blades. Borough names are repeated in radiating patterns and overlaid with the gradient. Red is still central to the charity’s identity, but FORM introduced the vivid orange worn by medics on-scene. “These colours blend in the gradient, creating a visual signature that speaks to urgency, action, optimism and hope,” says Alex Andlaw. https://d3faj0w6aqatyx.cloudfront.net/uploads/2025/06/LAA_OOH_TUBE_1920x1080.mp4 With the help of motion graphics designer Matt Fowler, the agency introduced movement to the branding, to reflect the aircraft’s blades in flight. The logo’s new wordmark is in Barlow, inspired by the existing big white lettering on the helicopter tail booms. Before, the charity’s name was written lower case in a thinner font. “Now it’s bigger, bolder and more impactful,” says Alex Andlaw. FORM also redesigned the icons to have more personality but still be functional. “The icons help the team talk about quite hard subjects,” he says, such as casualties, and the designs had to balance warmth and realism. “We did quite a few hearts, some look too detailed and some too basic,” he explains. The agency also created a series of collectible badges, inspired by the embroidered badges worn by the charity’s doctors and pilots.FORM Brands Studio identity for London’s Air Ambulance Charity in Instagram posts Meanwhile, photographer James Pearson-Howes was briefed to capture real people, places and moments from across London. The new branding had to resonate with very different types of donors, from the charity’s collection buckets to seven-figure corporate donations, says Clarke. “And the doctors wearing the brand have very strong opinions, as do the pilots. FORM took in all these views and managed to make all those people happy.” https://d3faj0w6aqatyx.cloudfront.net/uploads/2025/06/LAA_OOH_BILLBOARD_1920x1080.mp4 FORM Brands Studio identity for London’s Air Ambulance Charity FORM Brands Studio identity for London’s Air Ambulance Charity in OOH posters

Email authentication protocols like SPF, DKIM, and DMARC play a critical role in protecting domains from spoofing and phishing. However, when SEGs are introduced into the email path, the interaction with these protocols becomes more complex. Security gateways(SEGs) are a core part of many organizations’ email infrastructure. They act as intermediaries between the public internet and internal mail systems, inspecting, filtering, and routing messages. This blog examines how security gateways handle SPF, DKIM, and DMARC, with real-world examples from popular gateways such as Proofpoint, Mimecast, and Avanan. We’ll also cover best practices for maintaining authentication integrity and avoiding misconfigurations that can compromise email authentication or lead to false DMARC failures. Security gateways often sit at the boundary between your organization and the internet, managing both inbound and outbound email traffic. Their role affects how email authentication protocols behave. An inbound SEG examines emails coming into your organization. It checks SPF, DKIM, and DMARC to determine if the message is authentic and safe before passing it to your internal mail servers. An outbound SEG handles emails sent from your domain. It may modify headers, rewrite envelope addresses, or even apply DKIM signing. All of these can impact SPF,  DKIM, or DMARC validation on the recipient’s side. Understanding how SEGs influence these flows is crucial to maintaining proper authentication and avoiding unexpected DMARC failures. Inbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When an email comes into your organization, your security gateway is the first to inspect it. It checks whether the message is real, trustworthy, and properly authenticated. Let’s look at how different SEGs handle these checks. Avanan (by Check Point) SPF: Avanan verifies whether the sending server is authorized to send emails for the domain by checking the SPF record. DKIM: It verifies if the message was signed by the sending domain and if that signature is valid. DMARC: It uses the results of the SPF and DKIM check to evaluate DMARC. However, final enforcement usually depends on how DMARC is handled by Microsoft 365 or Gmail, as Avanan integrates directly with them. Avanan offers two methods of integration:1. API integration: Avanan connects via APIs, no change in MX, usually Monitor or Detect modes.2. Inline integration: Avanan is placed inline in the mail flow (MX records changed), actively blocking or remediating threats. Proofpoint Email Protection SPF: Proofpoint checks SPF to confirm the sender’s IP is authorized to send on behalf of the domain. You can set custom rules (e.g. treat “softfail” as “fail”). DKIM: It verifies DKIM signatures and shows clear pass/fail results in logs. DMARC: It fully evaluates DMARC by combining SPF and DKIM results with alignment checks. Administrators can configure how to handle messages that fail DMARC, such as rejecting, quarantining, or delivering them. Additionally, Proofpoint allows whitelisting specific senders you trust, even if their emails fail authentication checks. Integration Methods Inline Mode: In this traditional deployment, Proofpoint is positioned directly in the email flow by modifying MX records. Emails are routed through Proofpoint’s infrastructure, allowing it to inspect and filter messages before they reach the recipient’s inbox. This mode provides pre-delivery protection and is commonly used in on-premises or hybrid environments. API-Based (Integrated Cloud Email Security – ICES) Mode: Proofpoint offers API-based integration, particularly with cloud email platforms like Microsoft 365 and Google Workspace. In this mode, Proofpoint connects to the email platform via APIs, enabling it to monitor and remediate threats post-delivery without altering the email flow. This approach allows for rapid deployment and seamless integration with existing cloud email services. Mimecast SPF: Mimecast performs SPF checks to verify whether the sending server is authorized by the domain’s SPF record. Administrators can configure actions for SPF failures, including block, quarantine, permit, or tag with a warning. This gives flexibility in balancing security with business needs. DKIM: It validates DKIM signatures by checking that the message was correctly signed by the sending domain and that the content hasn’t been tampered with. If the signature fails, Mimecast can take actions based on your configured policies. DMARC: It fully evaluates DMARC by combining the results of SPF and DKIM with domain alignment checks. You can choose to honor the sending domain’s DMARC policy (none, quarantine, reject) or apply custom rules, for example, quarantining or tagging messages that fail DMARC regardless of the published policy. This allows more granular control for businesses that want to override external domain policies based on specific contexts. Integration Methods Inline Deployment: Mimecast is typically deployed as a cloud-based secure email gateway. Organizations update their domain’s MX records to point to Mimecast, so all inbound (and optionally outbound) emails pass through it first. This allows Mimecast to inspect, filter, and process emails before delivery, providing robust protection. API Integrations: Mimecast also offers API-based services through its Mimecast API platform, primarily for management, archival, continuity, and threat intelligence purposes. However, API-only email protection is not Mimecast’s core model. Instead, the APIs are used to enhance the inline deployment, not replace it. Barracuda Email Security Gateway SPF: Barracuda checks the sender’s IP against the domain’s published SPF record. If the check fails, you can configure the system to block, quarantine, tag, or allow the message, depending on your policy preferences. DKIM: It validates whether the incoming message includes a valid DKIM signature. The outcome is logged and used to inform further policy decisions or DMARC evaluations. DMARC: It combines SPF and DKIM results, checks for domain alignment, and applies the DMARC policy defined by the sender. Administrators can also choose to override the DMARC policy, allowing messages to pass or be treated differently based on organizational needs (e.g., trusted senders or internal exceptions). Integration Methods Inline mode (more common and straightforward): Barracuda Email Security Gateway is commonly deployed inline by updating your domain’s MX records to point to Barracuda’s cloud or on-premises gateway. This ensures that all inbound emails pass through Barracuda first for filtering and SPF, DKIM, and DMARC validation before being delivered to your mail servers. Deployment Behind the Corporate Firewall: Alternatively, Barracuda can be deployed in transparent or bridge mode without modifying MX records. In this setup, the gateway is placed inline at the network level, such as behind a firewall, and intercepts mail traffic transparently. This method is typically used in complex on-premises environments where changing DNS records is not feasible. Cisco Secure Email (formerly IronPort) Cisco Secure Email acts as an inline gateway for inbound email, usually requiring your domain’s MX records to point to the Cisco Email Security Appliance or cloud service. SPF: Cisco Secure Email verifies whether the sending server is authorized in the sender domain’s SPF record. Administrators can set detailed policies on how to handle SPF failures. DKIM: It validates the DKIM signature on incoming emails and logs whether the signature is valid or has failed. DMARC: It evaluates DMARC by combining SPF and DKIM results along with domain alignment checks. Admins can configure specific actions, such as quarantine, reject, or tag, based on different failure scenarios or trusted sender exceptions. Integration methods On-premises Email Security Appliance (ESA): You deploy Cisco’s hardware or virtual appliance inline, updating MX records to route mail through it for filtering. Cisco Cloud Email Security: Cisco offers a cloud-based email security service where MX records are pointed to Cisco’s cloud infrastructure, which filters and processes inbound mail. Cisco Secure Email also offers advanced, rule-based filtering capabilities and integrates with Cisco’s broader threat protection ecosystem, enabling comprehensive inbound email security. Outbound Handling of SPF, DKIM, and DMARC by Common Security Gateways When your organization sends emails, security gateways can play an active role in processing and authenticating those messages. Depending on the configuration, a gateway might rewrite headers, re-sign messages, or route them through different IPs – all actions that can help or hurt the authentication process. Let’s look at how major SEGs handle outbound email flow. Avanan – Outbound Handling and Integration Methods Outbound Logic Avanan analyzes outbound emails primarily to detect data loss, malware, and policy violations. In API-based integration, emails are sent directly by the original mail server (e.g., Microsoft 365 or Google Workspace), so SPF and DKIM signatures remain intact. Avanan does not alter the message or reroute traffic, which helps maintain full DMARC alignment and domain reputation. Integration Methods 1. API Integration: Connects to Microsoft 365 or Google Workspace via API. No MX changes are needed. Emails are scanned after they are sent, with no modification to SPF, DKIM, or the delivery path.  How it works: Microsoft Graph API or Google Workspace APIs are used to monitor and intervene in outbound emails. Protection level: Despite no MX changes, it can offer inline-like protection, meaning it can block, quarantine, or encrypt emails before they are delivered externally. SPF/DKIM/DMARC impact: Preserves original headers and signatures since mail is sent directly from Microsoft/Google servers. 2. Inline Integration: Requires changing MX records to route email through Avanan. In this mode, Avanan can intercept and inspect outbound emails before delivery. Depending on the configuration, this may affect SPF or DKIM if not properly handled. How it works: Requires adding Avanan’s Protection level: Traditional inline security with full visibility and control, including encryption, DLP, policy enforcement, and advanced threat protection. SPF/DKIM/DMARC impact: SPF configuration is needed by adding Avanan’s include mechanism to the sending domain’s SPF record. The DKIM record of the original sending source is preserved. For configurations, you can refer to the steps in this blog. Proofpoint – Outbound Handling and Integration Methods Outbound Logic Proofpoint analyzes outbound emails to detect and prevent data loss (DLP), to identify advanced threats (malware, phishing, BEC) originating from compromised internal accounts, and to ensure compliance. Their API integration provides crucial visibility and powerful remediation capabilities, while their traditional gateway (MX record) deployment delivers true inline, pre-delivery blocking for outbound traffic. Integration methods 1. API Integration: No MX record changes are required for this deployment method. Integration is done with Microsoft 365 or Google Workspace. How it works: Through its API integration, Proofpoint gains deep visibility into outbound emails and provides layered security and response features, including: Detect and alert: Identifies sensitive content (Data Loss Prevention violations), malicious attachments, or suspicious links in outbound emails. Post-delivery remediation (TRAP): A key capability of the API model is Threat Response Auto-Pull (TRAP), which enables Proofpoint to automatically recall, quarantine, or delete emails after delivery. This is particularly useful for internally sent messages or those forwarded to other users. Enhanced visibility: Aggregates message metadata and logs into Proofpoint’s threat intelligence platform, giving security teams a centralized view of outbound risks and user behavior. Protection level: API-based integration provides strong post-delivery detection and response, as well as visibility into DLP incidents and suspicious behavior.  SPF/DKIM/DMARC impact: Proofpoint does not alter SPF, DKIM, or DMARC because emails are sent directly through Microsoft or Google servers. Since Proofpoint’s servers are not involved in the actual sending process, the original authentication headers remain intact. 2. Gateway Integration (MX Record/Smart Host): This method requires updating MX records or routing outbound mail through Proofpoint via a smart host. How it works: Proofpoint acts as an inline gateway, inspecting emails before delivery. Inbound mail is filtered via MX changes; outbound mail is relayed through Proofpoint’s servers. Threat and DLP filtering: Scans outbound messages for sensitive content, malware, and policy violations. Real-time enforcement: Blocks, encrypts, or quarantines emails before they’re delivered. Policy controls: Applies rules based on content, recipient, or behavior. Protection level: Provides strong, real-time protection for outbound traffic with pre-delivery enforcement, DLP, and encryption. SPF/DKIM/DMARC impact: Proofpoint becomes the sending server: SPF: You need to configure ProofPoint’s SPF. DKIM: Can sign messages; requires DKIM setup. DMARC: DMARC passes if SPF and DKIM are set up properly. Please refer to this article to configure SPF and DKIM for ProofPoint. Mimecast – Outbound Handling and Integration Methods Outbound Logic Mimecast inspects outbound emails to prevent data loss (DLP), detect internal threats such as malware and impersonation, and ensure regulatory compliance. It primarily functions as a Secure Email Gateway (SEG), meaning it sits directly in the outbound email flow. While Mimecast offers APIs, its core outbound protection is built around this inline gateway model. Integration Methods 1. Gateway Integration (MX Record change required) This is Mimecast’s primary method for outbound email protection. Organizations route their outbound traffic through Mimecast by configuring their email server (e.g., Microsoft 365, Google Workspace, etc.) to use Mimecast as a smart host. This enables Mimecast to inspect and enforce policies on all outgoing emails in real time. How it works: Updating outbound routing in your email system (smart host settings), or Using Mimecast SMTP relay to direct messages through their infrastructure. Mimecast then scans, filters, and applies policies before the email reaches the final recipient. Protection level: Advanced DLP: Identifies and prevents sensitive data leaks. Impersonation and Threat Protection: Blocks malware, phishing, and abuse from compromised internal accounts. Email Encryption and Secure Messaging: Applies encryption policies or routes messages via secure portals. Regulatory Compliance: Enforces outbound compliance rules based on content, recipient, or metadata. SPF/DKIM/DMARC impact: SPF: Your SPF record must include Mimecast’s SPF mechanism based on your region to avoid SPF failures. DKIM: A new DKIM record should be configured to make sure your emails are DKIM signed when routing through Mimecast. DMARC: With correct SPF and DKIM setup, Mimecast ensures DMARC alignment, maintaining your domain’s sending reputation. Please refer to the steps in this detailed article to set up SPF and DKIM for Mimecast. 2. API Integration (Complementary to Gateway) Mimecast’s APIs complement the main gateway by providing automation, reporting, and management tools rather than handling live outbound mail flow. They allow you to manage policies, export logs, search archived emails, and sync users. APIs enhance visibility and operational tasks but do not provide real-time filtering or blocking of outbound messages. Since APIs don’t process live mail, they have no direct effect on SPF, DKIM, or DMARC; those depend on your gateway (smart host) setup. Barracuda – Outbound Handling and Integration Methods Outbound Logic Barracuda analyzes outbound emails to prevent data loss (DLP), block malware, stop phishing/impersonation attempts from compromised internal accounts, and ensure compliance. Barracuda offers flexible deployment options, including both traditional gateway (MX record) and API-based integrations. While both contribute to outbound security, their roles are distinct. Integration Methods 1. Gateway Integration (MX Record / Smart Host) — Primary Inline Security How it works: All outbound emails pass through Barracuda’s security stack for real-time inspection, threat blocking, and policy enforcement before delivery. Protection level: Comprehensive DLP (blocking, encrypting, or quarantining sensitive content)  Outbound spam and virus filtering  Enforcement of compliance and content policies This approach offers a high level of control and immediate threat mitigation on outbound mail flow. SPF/DKIM/DMARC impact: SPF: Update SPF records to include Barracuda’s sending IPs or SPF include mechanism. DKIM: Currently, no explicit setup is needed; DKIM of the main sending source is preserved. Refer to this article for more comprehensive guidance on Barracuda SEG configuration. 2. API Integration (Complementary & Advanced Threat Focus) How it works: The API accesses cloud email environments to analyze historical and real-time data, learning normal communication patterns to detect anomalies in outbound emails. It also supports post-delivery remediation, enabling the removal of malicious emails from internal mailboxes after sending. Protection level: Advanced AI-driven detection and near real-time blocking of outbound threats, plus strong post-delivery cleanup capabilities. SPF/DKIM/DMARC impact: Since mail is sent directly by the original mail server (e.g., Microsoft 365), SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. Cisco Secure Email (formerly IronPort) – Outbound Handling and Integration Methods Outbound Logic Cisco Secure Email protects outbound email by preventing data loss (DLP), blocking spam and malware from internal accounts, stopping business email compromise (BEC) and impersonation attacks, and ensuring compliance. Cisco provides both traditional gateway appliances/cloud gateways and modern API-based solutions for layered outbound security. Integration Methods 1. Gateway Integration (MX Record / Smart Host) – Cisco Secure Email Gateway (ESA) How it works: Organizations update MX records to route mail through the Cisco Secure Email Gateway or configure their mail server (e.g., Microsoft 365, Exchange) to smart host outbound email via the gateway. All outbound mail is inspected and policies enforced before delivery. Protection level: Granular DLP (blocking, encrypting, quarantining sensitive content) Outbound spam and malware filtering to protect IP reputation Email encryption for sensitive outbound messages Comprehensive content and attachment policy enforcement SPF: Check this article for comprehensive guidance on Cisco SPF settings. DKIM: Refer to this article for detailed guidance on Cisco DKIM settings. 2. API Integration – Cisco Secure Email Threat Defense How it works: Integrates directly via API with Microsoft 365 (and potentially Google Workspace), continuously monitoring email metadata, content, and user behavior across inbound, outbound, and internal messages. Leverages Cisco’s threat intelligence and AI to detect anomalous outbound activity linked to BEC, account takeover, and phishing. Post-Delivery Remediation: Automates the removal or quarantine of malicious or policy-violating emails from mailboxes even after sending. Protection level: Advanced, AI-driven detection of sophisticated outbound threats with real-time monitoring and automated remediation. Complements gateway filtering by adding cloud-native visibility and swift post-send action. SPF/DKIM/DMARC impact: Since emails are sent directly by the original mail server, SPF and DKIM signatures remain intact, preserving DMARC alignment and domain reputation. If you have any questions or need assistance, feel free to reach out to EasyDMARC technical support.

Posted on : June 5, 2025 By Tech World Times Technology  Rate this post The Software as a Service (SaaS) industry has been on an unstoppable trajectory since its inception, revolutionizing how businesses and individuals consume and manage software. The landscape of subscription services within this sector continues to evolve at a rapid pace. Driven by customer expectations, technological advancements, and economic shifts, several trends are emerging that promise to reshape the SaaS industry. These trends will not only influence the way software is delivered and managed but also impact the overall subscription economy. Check out these subscription trends that are set to redefine the SaaS industry in the next few years. 1. Personalization and Customer-Centric Models Businesses are increasingly recognizing the value of tailored experiences, and SaaS companies are responding with personalized subscription offerings. By leveraging user data and machine learning algorithms, providers are crafting customized solutions that cater to individual needs, preferences, and usage patterns. Personalization also extends to the billing process, where SaaS payment processing systems are adapting to offer flexible pricing models, such as pay-per-use and tiered subscriptions. 2. Integrated Payment Solutions and Subscription Management SaaS payment processing will become a seamless and integrated part of the subscription experience. Innovations in financial technology will streamline the billing process, providing users with a unified dashboard to manage all their subscriptions. This will simplify financial management for both consumers and businesses. Companies will be able to offer various payment methods, automate billing cycles, and handle currency conversions with ease, making it easier for them to serve a global customer base. 3. The Rise of Usage-Based Pricing Usage-based pricing is gaining traction as a fair and transparent way to bill for cloud services. Instead of flat monthly or annual fees, SaaS providers will charge customers based on the actual resources consumed. This model aligns the cost with the value derived, encouraging more efficient use of resources and reducing waste. It also allows companies to scale more easily, leading to more granular and sophisticated pricing structures that can handle these complex calculations. 4. Subscription Model Innovation To stand out in a crowded market, SaaS companies are experimenting with innovative subscription models that go beyond the typical monthly or annual plans. These include freemium models, where users get a basic version of the software for free and pay for additional features, and dynamic pricing that adjusts based on demand and supply. The goal is to create a more nuanced pricing strategy that appeals to a wider range of customers and enhances the overall perceived value of the service. 5. Emphasis on User Experience and Customer Retention The importance of user experience is paramount in the SaaS industry, and in 2025, companies will invest heavily in creating delightful onboarding processes, intuitive user interfaces, and proactive customer support. The focus on customer retention will be a key driver for subscription growth, as it becomes more cost-effective than acquiring new ones. This shift will lead to the integration of more sophisticated tools for tracking customer engagement and satisfaction, allowing for targeted interventions to reduce churn rates. 6. Expansion into Emerging Markets As developed markets become saturated, SaaS companies are setting their sights on emerging economies. To cater to these diverse markets, providers will need to adapt their offerings to suit local preferences and constraints, such as language, cultural nuances, and payment methods. This trend will result in the rise of regional SaaS leaders and increased competition from local players, pushing the industry to become more global and inclusive. 7. Increased Adoption of AI and Automation Artificial intelligence and automation will play a significant role in the SaaS industry, optimizing everything from customer support to sales and marketing. Chatbots and virtual assistants will become commonplace for handling routine inquiries, while AI algorithms will be used to predict customer behavior and offer personalized recommendations. Automation will streamline backend processes, reducing costs and enhancing the overall efficiency of subscription management. This integration will lead to more intelligent and proactive services, with the potential for predictive analytics to anticipate customer needs before they even arise. The SaaS industry is poised for continued growth and evolution, with these seven subscription trends at the forefront. Personalization, integrated payment processing, usage-based pricing, innovative models, user experience enhancements, emerging market expansion, and the integration of AI and automation are all shaping the future of this dynamic sector. The most successful SaaS companies will be those that embrace these trends, adapting their offerings and operations to meet the changing demands of the modern subscription economy. With the right strategies in place, they will be able to deliver superior value to their customers and thrive in an increasingly competitive landscape. Tech World TimesTech World Times (TWT), a global collective focusing on the latest tech news and trends in blockchain, Fintech, Development & Testing, AI and Startups. If you are looking for the guest post then contact at techworldtimes@gmail.com

Larry Fabbroni is an architect, strategic advisor, and Chief Innovation Officer for Practice of Architecture. Throughout his career, he has led efforts to reform studio culture and innovate practice. He earned his MBA from the University of Chicago’s Booth School of Business. In 2017, as leaders in the AIA’s Young Architects Forum (YAF), we led the launch of the Practice Innovation Lab (PIL) and hosted a symposium that imagined new architectural practice models. At that time, we already felt that practice innovation was overdue in a profession that has not seen scaled disruption to its business model in over a century. Today, we are confident that there has never been a more critical time for the profession to embrace innovation. Redefining Innovation Henley Hall: Institute for Energy Efficiency by KieranTimberlake, Santa Barbara, California | KieranTimberlake’s research expertise creates value beyond a baseline labor model.  Currently, artificial intelligence dominates strategy conversations, but just as we saw back in 2017, larger patterns prompt calls for innovation. Talent attraction is increasingly challenging, disruptive technology continues to emerge, and actors from outside our industry show growing interest in the space. While incremental innovation has long been a part of the profession, relatively few firms have adopted new practices that create value beyond a baseline labor model. Firms such as KieranTimberlake have shown that research expertise can do this. MASS Design has pioneered a mission-driven approach. BIG has taken on the role of architect-as-developer. Snøhetta houses a product design division. We could continue to list great firms that have pushed the boundaries of practice, but they represent exceptions that have yet to be recognized as new standards. Indeed, the confluence of those factors that led to the original PIL continues to make the case that the time for scaled innovation is now. A Melting Iceberg: Incremental Changes Depleting the Profession Powerhouse Telemark by Snøhetta, Vestfold og Telemark, Norway | Photo by Ivar Kvaal | Snøhetta houses a product design division, innovatively presenting a alternative business model for firms.  One of the dangers of operating in a slow-moving industry is that change is difficult to detect and even more challenging to comprehend. If an iceberg loses 1% of mass per year, it’s tough to take notice, but the end result is catastrophic. This is what is happening to our profession. For newcomers, if it feels like there are increasingly more attractive opportunities elsewhere, that’s because there are. For seasoned professionals, if it feels like it’s become more challenging to maintain the same levels of prosperity, that’s because it has. Less(er) Talent In some ways, the shift towards companies recognizing “talent” as their most excellent resource has bewildered architects: we have always relied on talent. However, the patterns of talent leaving our profession are concerning. We say “feel” because there is no significant data. We spoke to Kendall A. Nicholson, Senior Director of Research at the Association of Collegiate Schools of Architecture (ACSA), who confirmed that aggregated data on graduate placement does not exist. So we inquired about what placement looks like at several programs around the country. Omar Khan, Head of the Carnegie Mellon University School of Architecture, informed us that approximately 90% of students pursue a minor to expand their horizons, and that in 2022, nearly one in three graduates entered the tech sector. Khan stated that these opportunities aren’t just student-driven — large innovative companies increasingly seek the value that graduates of architecture schools will provide. This increasing difficulty in capturing the talent that architecture schools are producing results in a shrinking and diluted talent pool. For a profession so reliant on human resources, this presents extreme risk. Pay Gaps In an increasingly expensive world, we are not able to compete for the best talent with emerging industries. It’s easy to understand why a popular career pivot for architects has become UX design. Designing user experience for websites pays significantly better than designing the same for the built environment. According to Glassdoor, 2023 entry-level UX designers earned an average of $78K, while the AIA salary calculator suggests architecture grads can expect to earn an average of $59 K. The talent we do attract into the profession often loses interest when they experience low pay and long hours, all while most firms lack clear paths and criteria for advancement or compensation increases. A Smaller Piece of the Pie Examining data in isolation, one might conclude that the profession continues to grow; the number of architects has increased substantially over the last century, and this trend has persisted in recent years. The problem with this growth is that the estimated share of the US GDP for Architectural Services has shrunk over time. This is not a manageable number to measure before 1999, when NCARB first aggregated local jurisdictional data. Due to limitations in industry economic data, we’re only showing data since 2011 for the purposes of this article. In that time, the number of architects has grown, the market size for services has grown, but the share those services represent as a portion of the US GDP has declined — by 15% if we use US Census data to almost 30% if we use industry research data (we used IbisWorld.com, however we found data that suggested a worse and others that offered a slightly better picture). To put it another way, architecture is a stagnant industry with a shrinking share of the economy. It’s challenging to examine this data and emerge feeling confident about the profession, but there is a silver lining. The biggest impediment to innovation for architects is not a lack of talent, but rather the business model. Design thinking has been widely adopted throughout the world as a key component of innovation processes; however, the problem is that we operate in the realm of professional services, which inherently is not well-suited to promoting innovation. Reliance on that formula is causing our iceberg to melt. The Tsunami: The AI Tidal Wave is Here The Rwanda Institute for Conservation Agriculture by MASS Design Group, Rwanda | MASS Design has pioneered a mission-driven approach that creates value beyond a baseline labor model.  As we confront the exodus of talent, it is easy for both firm owners and clients to imagine AI bringing efficiencies and replacing “CAD-monkeys” with machines. However, any firm that wants to operate — and win — as anything more than a low-cost provider will need a strategy to increase value, not just cut costs. AI is merely part of the toolbox required to confront a perfect storm of forces. Jobs will Disappear Goldman Sachs predicts that as much as 37% of our industry tasks will be replaced by AI. Many see this as a pathway to lower costs and increased profits. However, that is short-sighted. Markets will adjust quickly and demand lower costs for services; additional new value will need to be articulated and proven, and this will only happen through innovation. New Jobs will Emerge (but fewer of them) AI prophets often emphasize that technological innovation has historically led to net employment gains. Previous World Economic Forum estimates predicted losses of up to 85 million existing jobs worldwide, with parallel gains of as many as 97 million new jobs. However, these estimates were revised in the WEF 2023 Economic Outlook, which now anticipates a net loss of 14 million jobs. This stark outlook signals an even greater need for architects to become more innovative. The 2024 RIBA AI Report indicates that 41% of architecture firms were already utilizing AI, though current tools are indeed just the beginning. Marketing, business development and content creation will be standard areas of AI deployment moving forward. Still, revolutionary changes will come in how we learn, not only to use new tools, but also to collaborate with digital agents. How will this happen? We can theorize, but it is not possible to know for sure until it arrives, so we need to have a plan before we can see the tidal wave from land. The Alien Invasion: Outsiders Are Entering Our Orbit VIA 57 West by BIG – Bjarke Ingels Group, New York City, New York | BIG has pioneered a new model for practice by taking on the role of architect-as-developer. For years, we’ve heard cries that “architects gave away the role of master builder.” But how much did architects actually give, and how much was taken by innovative competition? This distinction is critical because the wagons are circling, and the AEC space has become ever more attractive to investors. Venture Capital and Private Equity Investment The numbers are often difficult to parse because architecture can impact so many verticals and does not operate as its own sector in the investment realm; however, the trends suggest a groundswell is underway. A 2023 McKinsey report shows that construction tech deals nearly doubled from 2019 to 2022, growing by 85%. At the same period, the number of deals increased by 30%, indicating that interest continues to grow. An increasing size of deals also suggests a maturity of the market. As interest in infrastructure investments has declined from its high in 2020, and along with real estate, has been blunted by high interest rates, institutional investors continue to see opportunities in the AEC space. Firm Acquisitions AEC firms that deliver predictable returns have proven to be attractive targets for PE firms. In the second quarter of 2024, private equity firms accounted for over one-third of AEC firm mergers and acquisitions. For M&A deals, the industry has seen an increase in attractiveness with expanded infrastructure spending as a catalyst. However, this interest can also be tied to the lack of innovation that has resulted in an industry ripe for consolidation. M&A orchestrators generate large amounts of profit by streamlining operations, eliminating redundancies, and then stamping out competition. An entire community has been built around this, with AEC Advisors hosting an annual “Private Equity Summit” that brings together CEOs of AEC firms with PE investors. Startups As an extension of the growing interest from venture capital in the space, there is an upward trend in the AEC space being targeted for disruption by entrepreneurs who see an industry that represents a significant portion of the global GDP. AEC Works, a project of e-verse that catalogs AEC startups and investors, lists nearly 800 startups from around the world, with almost 200 identified as “architecture-focused.” The signal is clear: startups are looking to figure out how to do what you do cheaper, better, or perhaps both. Combining this environment with depleted talent pools, a declining share of GDP, and revolutionary technology, it is a correct response to be alarmed. Significant change is inevitable. It is time for architects to see the same opportunities that investors and entrepreneurs see, and learn to navigate within these spaces. The Great Opportunity Throughout history, new actors have enjoyed a “leap-frog” effect and been able to surpass established incumbents to reshape industries, markets and economies. From climate change to pandemic ripple effects, to the housing crisis, to generational shifts in the workforce, there are many forces that directly impact the work of architects and call for innovation. The need for new ways of designing and delivering different components of the built environment is ever-present and will be solved by teams that either include — and might be led by — architects, or those that do not. Most end users will only care if the resulting product is superior. This time of tension is indeed a time of great opportunity. Architects who embrace innovation in pursuing new iterations of our dated business models may actually achieve what many of us have dreamed of from the start: to leave a positive mark on the world. We think the future of the profession depends on it. Top image: Powerhouse Telemark by Snøhetta, Vestfold og Telemark, Norway The post Architects, Your Real Competition Isn’t AI — It’s Business Complacency appeared first on Journal.

Why building trust matters more than building components.There’s a scene in Field of Dreams that regularly comes to mind. Ray Kinsella (Kevin Costner) is standing at the edge of his cornfield ballpark, full of doubt about his ball field project. And then Terrence Mann (James Earl Jones) delivers this quiet but powerful monologue…James Earl Jones as Terrence Mann gives an inspiring speech“People will come, Ray. They’ll come to Iowa for reasons they can’t even fathom… They’ll arrive at your door as innocent as children, longing for the past… They’ll pass over the money without even thinking about it — for it is money they have and peace they lack.”It’s powerful. And there’s temptation for designers to think this way. That, if we just build it properly, people will come and use it. It’ll be a raving success. But that kind of thinking rests on emotion and hope. “People will come, Ray.”That got me thinking about my work with design systems. Because early on, that’s exactly how I imagined it would work.No…they won’t just come.I thought if you just built a great design system, people would come running from all over to use it. Designers would geek out. Engineers would contribute. PMs would rally around the time savings and consistency. I thought the system would basically sell itself. Job done.Except not. Not at first. In fact, most of those people actively resisted it. And it left me frustrated trying to figure out what was going on.That’s when it hit me: people don’t come just because you built something. They come because you built something that includes them. This isn’t a fictional baseball field built on faith. They don’t come because they don’t know it. It’s foreign. And as humans, we tend to run away from what we don’t understand.That’s why the people who work on design systems are so important. So that you can be known and your systems can be known. So that a relationship can be established. Trust can be created and people can see that this system will work for them. In fact, it’s been purpose-built for them.Design Systems are political (it’s true)I never would have imagined how political design systems would be. They seem logical and straightforward. It’s everything you need to build interfaces and consistent experiences. So, I thought the quality of the work would speak for itself. But once your system meets the real world, things get complicated. Real fast.Everyone already has established working patterns and people aren’t usually inclined to change. Plus, designers have their opinions. Engineers have priorities. Product managers have launch dates. And everyone already has a “good-enough solution”. So, now your carefully crafted design system feels more like a threat or liability than the life-changing birthday present you thought it’d be.You thought you were offering something amazing. They hear restriction. They see more steps. And they’re annoyed — at you — for meddling in their perfectly stable world.Why? Well, people love their tools. And, I mean LOVE them. They deeply cherish them. I think of the carpenter who’s used the same, trusty 20oz wood-handled hammer for 40 years. It’s weathered difficult projects and has dents and stains from 1,000s of projects. How do you convince someone to leave that hammer behind and pick up a new, unproven hammer for their work? It usually happens in community…in relationships.So, it turns out, building the system was the easy part. Getting people to care about it? That’s the real work. And that’s where building relationships comes in.The real work: building relationshipsTrue adoption doesn’t happen through documentation or a flashy campaign.So you can’t rely on a “build it and they will come” mentality. It means you need to make time to understand the people you’re building for and with. Because if it isn’t theirs, it won’t matter how good it is. Every group has different motivations, pain points, and goals. If you want them on board, you have to speak to them, about them, and how your system will help them.Designers need to see how the system supports creativity, not stifles it. Demonstrate how it will help them be more effective in their work.Engineers care about stability, performance, and clean code. Show them the efficiency that it brings to their development pipelines.PMs are focused on delivery. Make the system reduce friction and risk.Executives want the business case to be clear. Show them how your system enables faster velocity, better consistency, and reduced maintenance cost.Establishing how individual goals come together as shared goals is critical.Sounds selfish, right? Not really. They’re paid to do their job, and if you want your design system to be successful, it has to make them successful. So if you can’t answer a need to any of your partners or stakeholders, go back and figure out how to create that kind of value…or start with the people where the value already is.It’s the relationships that shift the dynamic. Suddenly it’s not “my design system vs. their priorities”…it’s shared ownership…our collective win.You can’t enforce your way to powerful adoptionYour first instinct might be to skip the relationships and rely on the “because I said so” method. So you add mandates. Governance councils. Approval gates. But none of them really work. You’ll have people subvert the system, or hold so fearfully tight to it that it hurts the product experience in the end.People don’t adopt systems because they have to. They adopt them because they believe in them. And belief is earned, not enforced. Your job is to find the intrinsic motivation that will cause them to jump on board and be a raving fan spreading the good news of your system. And that can’t be a marketing slogan or tagline; it has to be built into the design system.The goal isn’t to control usage…it’s to cultivate trust, leading to usage. It’s better to have ten enthusiastic partners than a hundred reluctant rule-followers. Because those ten partners? They’ll advocate for you. They’ll give real feedback. They’ll make the system better.It sounds uncomfortable, but it’s best to trade policing behavior for building partnerships. That’s the moment your system will truly grow. Because trust is a currency that earns interest.Trust is the real foundationDesign systems rely on a strong foundation: principles, guidelines, tokens, styles, components, and more. But that foundation must be built on something critical: trust.Trust is what makes someone choose the system instead of rolling their own. It’s what keeps your system on their radar when everything’s on fire. It’s what makes people reach out to work it out together, instead of working around you and subverting the whole thing.Without trust, your system is just a nice idea. It’s relegated to pixel art. But with relationships that foster trust…they see how the system becomes indispensable. It’s their go-to secret weapon for success.Trust and relationships are the ground that all foundations are built on.I’ve been on both sides. I’ve had teams avoid the system because they didn’t trust it…because they didn’t trust me. Here’s the secret: I know them or how to serve them…no trust. On the flip side, I’ve seen teams move faster, smoother, and more confidently because we’d built a foundation of partnership over time.Trust isn’t a side effect. It’s not a nice-to-have. It’s the ground that holds the whole thing up. Without it, your design system is drifting in the outer cosmos. Relationships are the gravity that keeps your design system grounded in trust.They’ll come… but only if you earn itSo, I hate to break it to you, but the truth is…no one’s coming just because your system is well-made. There’s already a plethora of well-made systems out there ready to leave you disappointed.They’re busy with the newest top priority. They’ve been burned by “that type of system” before. They see you as a risk, not a partner. But…if you spend time knowing them… if you listen… if you build trust… if you make it feel like it’s theirs… well then… “…they will come…”They’ll message you before they start a new feature. They’ll advocate for tokens during sprint planning. They’ll tell others it saved them time. They’ll ask how they can help improve it.They won’t come for the components. They’ll come for what the system gives them: clarity. Consistency. Relief.And if you’ve done the hard, human work behind the system? Well then, you might just look up one day and realize that there’s a whole bunch of people in your Iowa ball field.The politics of Design Systems was originally published in UX Collective on Medium, where people are continuing the conversation by highlighting and responding to this story.

When people talk about UX, it’s usually about the things they can see and interact with, like wireframes and prototypes, smart interactions, and design tools like Figma, Miro, or Maze. Some of the outputs are even glamorized, like design systems, research reports, and pixel-perfect UI designs. But here’s the truth I’ve seen again and again in over two decades of working in UX: none of that moves the needle if there is no collaboration. Great UX doesn’t happen in isolation. It happens through conversations with engineers, product managers, customer-facing teams, and the customer support teams who manage support tickets. Amazing UX ideas come alive in messy Miro sessions, cross-functional workshops, and those online chats (e.g., Slack or Teams) where people align, adapt, and co-create. Some of the most impactful moments in my career weren’t when I was “designing” in the traditional sense. They have been gaining incredible insights when discussing problems with teammates who have varied experiences, brainstorming, and coming up with ideas that I never could have come up with on my own. As I always say, ten minds in a room will come up with ten times as many ideas as one mind. Often, many ideas are the most useful outcome. There have been times when a team has helped to reframe a problem in a workshop, taken vague and conflicting feedback, and clarified a path forward, or I’ve sat with a sales rep and heard the same user complaint show up in multiple conversations. This is when design becomes a team sport, and when your ability to capture the outcomes multiplies the UX impact. Why This Article Matters Now The reason collaboration feels so urgent now is that the way we work since COVID has changed, according to a study published by the US Department of Labor. Teams are more cross-functional, often remote, and increasingly complex. Silos are easier to fall into, due to distance or lack of face-to-face contact, and yet alignment has never been more important. We can’t afford to see collaboration as a “nice to have” anymore. It’s a core skill, especially in UX, where our work touches so many parts of an organisation. Let’s break down what collaboration in UX really means, and why it deserves way more attention than it gets. What Is Collaboration In UX, Really? Let’s start by clearing up a misconception. Collaboration is not the same as cooperation. Cooperation: “You do your thing, I’ll do mine, and we’ll check in later.” Collaboration: “Let’s figure this out together and co-own the outcome.” Collaboration, as defined in the book Communication Concepts, published by Deakin University, involves working with others to produce outputs and/or achieve shared goals. The outcome of collaboration is typically a tangible product or a measurable achievement, such as solving a problem or making a decision. Here’s an example from a recent project: Recently, I worked on a fraud alert platform for a fintech business. It was a six-month project, and we had zero access to users, as the product had not yet hit the market. Also, the users were highly specialised in the B2B finance space and were difficult to find. Additionally, the team members I needed to collaborate with were based in Malaysia and Melbourne, while I am located in Sydney. Instead of treating that as a dead end, we turned inward: collaborating with subject matter experts, professional services consultants, compliance specialists, and customer support team members who had deep knowledge of fraud patterns and customer pain points. Through bi-weekly workshops using a Miro board, iterative feedback loops, and sketching sessions, we worked on design solution options. I even asked them to present their own design version as part of the process. After months of iterating on the fraud investigation platform through these collaboration sessions, I ended up with two different design frameworks for the investigator’s dashboard. Instead of just presenting the “best one” and hoping for buy-in, I ran a voting exercise with PMs, engineers, SMEs, and customer support. Everyone had a voice. The winning design was created and validated with the input of the team, resulting in an outcome that solved many problems for the end user and was owned by the entire team. That’s collaboration! It is definitely one of the most satisfying projects of my career. On the other hand, I recently caught up with an old colleague who now serves as a product owner. Her story was a cautionary tale: the design team had gone ahead with a major redesign of an app without looping her in until late in the game. Not surprisingly, the new design missed several key product constraints and business goals. It had to be scrapped and redone, with her now at the table. That experience reinforced what we all know deep down: your best work rarely happens in isolation. As illustrated in my experience, true collaboration can span many roles. It’s not just between designers and PMs. It can also include QA testers who identify real-world issues, content strategists who ensure our language is clear and inclusive, sales representatives who interact with customers on a daily basis, marketers who understand the brand’s voice, and, of course, customer support agents who are often the first to hear when something goes wrong. The best outcomes arrive when we’re open to different perspectives and inputs. Why Collaboration Is So Overlooked? If collaboration is so powerful, why don’t we talk about it more? In my experience, one reason is the myth of the “lone UX hero”. Many of us entered the field inspired by stories of design geniuses revolutionising products on their own. Our portfolios often reflect that as well. We showcase our solo work, our processes, and our wins. Job descriptions often reinforce the idea of the solo UX designer, listing tool proficiency and deliverables more than soft skills and team dynamics. And then there’s the team culture within many organisations of “just get the work done”, which often leads to fewer meetings and tighter deadlines. As a result, a sense of collaboration is inefficient and wasted. I have also experienced working with some designers where perfectionism and territoriality creep in — “This is my design” — which kills the open, communal spirit that collaboration needs. When Collaboration Is The User Research In an ideal world, we’d always have direct access to users. But let’s be real. Sometimes that just doesn’t happen. Whether it’s due to budget constraints, time limitations, or layers of bureaucracy, talking to end users isn’t always possible. That’s where collaboration with team members becomes even more crucial. The next best thing to talking to users? Talking to the people who talk to users. Sales teams, customer success reps, tech support, and field engineers. They’re all user researchers in disguise! On another B2C project, the end users were having trouble completing the key task. My role was to redesign the onboarding experience for an online identity capture tool for end users. I was unable to schedule interviews with end users due to budget and time constraints, so I turned to the sales and tech support teams. I conducted multiple mini-workshops to identify the most common onboarding issues they had heard directly from our customers. This led to a huge “aha” moment: most users dropped off before the document capture process. They may have been struggling with a lack of instruction, not knowing the required time, or not understanding the steps involved in completing the onboarding process. That insight reframed my approach, and we ultimately redesigned the flow to prioritize orientation and clear instructions before proceeding to the setup steps. Below is an example of one of the screen designs, including some of the instructions we added. This kind of collaboration is user research. It’s not a substitute for talking to users directly, but it’s a powerful proxy when you have limited options. But What About Using AI? Glad you asked! Even AI tools, which are increasingly being used for idea generation, pattern recognition, or rapid prototyping, don’t replace collaboration; they just change the shape of it. AI can help you explore design patterns, draft user flows, or generate multiple variations of a layout in seconds. It’s fantastic for getting past creative blocks or pressure-testing your assumptions. But let’s be clear: these tools are accelerators, not oracles. As an innovation and strategy consultant Nathan Waterhouse points out, AI can point you in a direction, but it can’t tell you which direction is the right one in your specific context. That still requires human judgment, empathy, and an understanding of the messy realities of users and business goals. You still need people, especially those closest to your users, to validate, challenge, and evolve any AI-generated idea. For instance, you might use ChatGPT to brainstorm onboarding flows for a SaaS tool, but if you’re not involving customer support reps who regularly hear “I didn’t know where to start” or “I couldn’t even log in,” you’re just working with assumptions. The same applies to engineers who know what is technically feasible or PMs who understand where the business is headed. AI can generate ideas, but only collaboration turns those ideas into something usable, valuable, and real. Think of it as a powerful ingredient, but not the whole recipe. How To Strengthen Your UX Collaboration Skills? If collaboration doesn’t come naturally or hasn’t been a focus, that’s okay. Like any skill, it can be practiced and improved. Here are a few ways to level up: Cultivate curiosity about your teammates.Ask engineers what keeps them up at night. Learn what metrics your PMs care about. Understand the types of tickets the support team handles most frequently. The more you care about their challenges, the more they'll care about yours. Get comfortable facilitating.You don’t need to be a certified Design Sprint master, but learning how to run a structured conversation, align stakeholders, or synthesize different points of view is hugely valuable. Even a simple “What’s working? What’s not?” retro can be an amazing starting point in identifying where you need to focus next. Share early, share often.Don’t wait until your designs are polished to get input. Messy sketches and rough prototypes invite collaboration. When others feel like they’ve helped shape the work, they’re more invested in its success. Practice active listening.When someone critiques your work, don’t immediately defend. Pause. Ask follow-up questions. Reframe the feedback. Collaboration isn’t about consensus; it’s about finding a shared direction that can honour multiple truths. Co-own the outcome.Let go of your ego. The best UX work isn’t “your” work. It’s the result of many voices, skill sets, and conversations converging toward a solution that helps users. It’s not “I”, it’s “we” that will solve this problem together. Conclusion: UX Is A Team Sport Great design doesn’t emerge from a vacuum. It comes from open dialogue, cross-functional understanding, and a shared commitment to solving real problems for real people. If there’s one thing I wish every early-career designer knew, it’s this: Collaboration is not a side skill. It’s the engine behind every meaningful design outcome. And for seasoned professionals, it’s the superpower that turns good teams into great ones. So next time you’re tempted to go heads-down and just “crank out a design,” pause to reflect. Ask who else should be in the room. And invite them in, not just to review your work, but to help create it. Because in the end, the best UX isn’t just what you make. It’s what you make together. Further Reading On SmashingMag “Presenting UX Research And Design To Stakeholders: The Power Of Persuasion,” Victor Yocco “Transforming The Relationship Between Designers And Developers,” Chris Day “Effective Communication For Everyday Meetings,” Andrii Zhdan “Preventing Bad UX Through Integrated Design Workflows,” Ceara Crawshaw