惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

K
Kaspersky official blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
Cyberwarzone
Cyberwarzone
S
Securelist
S
Schneier on Security
V
Vulnerabilities – Threatpost
Latest news
Latest news
G
GRAHAM CLULEY
C
CERT Recently Published Vulnerability Notes
T
The Exploit Database - CXSecurity.com
Scott Helme
Scott Helme
Know Your Adversary
Know Your Adversary
雷峰网
雷峰网
S
SegmentFault 最新的问题
Jina AI
Jina AI
A
About on SuperTechFans
GbyAI
GbyAI
F
Full Disclosure
T
Tenable Blog
博客园 - 聂微东
P
Privacy International News Feed
Recorded Future
Recorded Future
PCI Perspectives
PCI Perspectives
MongoDB | Blog
MongoDB | Blog
L
LINUX DO - 热门话题
NISL@THU
NISL@THU
Microsoft Security Blog
Microsoft Security Blog
C
Check Point Blog
The GitHub Blog
The GitHub Blog
IT之家
IT之家
S
Secure Thoughts
Cloudbric
Cloudbric
S
Security @ Cisco Blogs
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
博客园_首页
N
News | PayPal Newsroom
有赞技术团队
有赞技术团队
I
Intezer
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
大猫的无限游戏
大猫的无限游戏
The Register - Security
The Register - Security
WordPress大学
WordPress大学
Hugging Face - Blog
Hugging Face - Blog
Martin Fowler
Martin Fowler
小众软件
小众软件
人人都是产品经理
人人都是产品经理
C
Cyber Attacks, Cyber Crime and Cyber Security
宝玉的分享
宝玉的分享
Schneier on Security
Schneier on Security

Giant Robots Smashing Into Other Giant Robots

Join us: Building Secure Healthcare Systems Upcase has retired, but the learning continues The Bike Shed Ep 506: The Muppet Software Team Migrating to native stack navigation, with a surprise from iOS 26 Past and present thoughtbotters at LRUG this Monday The Bike Shed Ep 505: What is a “principal” or “staff” engineer? Your vibe coded website is going to get you fined Roux’s New Component Library Why we're choosing stewardship over an exit The Bike Shed Ep 503: Seeing the Graph for the Trees Announcing Shoulda Matchers 8.0: validate multiple attributes in one line AI's "overnight" solution for our flaky tests took two weeks to adopt The Playwright debugging tool Rails devs aren't using Meet thoughtbot at Brighton Ruby 2026 614: AI Code Audits AI crawlers are inflating your view counts 502: Apps That Make Our Work Go Toast: the 2-minute test that reveals how you think about building products How I Built a Chrome Extension Wrapper (and Everything That Tried to Stop Me) Enforcing Your Ruby Style Guide on AI-Generated Code Copy as Markdown: AI-friendly blog posts 501: What makes for good technical writing? The Four Signals of AI Observability Can you really launch a tech business with a no-code app builder? 612: Do fish drink? This week in #dev (May 15, 2026) Lost, forgotten, and unfamiliar HTML 500: Celebrating with past hosts Why Duck Typer? Biometrics authentication for your mobile app
The mistake I didn't realise I was making when designing workshops
Bethan Ashley · 2026-06-17 · via Giant Robots Smashing Into Other Giant Robots

The checklist I expected

Last week I attended a workshop on neuroinclusivity in learning design.

I expected to come away with a checklist.

  • Use larger fonts
  • Send slides in advance
  • Offer cameras off
  • Use a dyslexia-friendly typeface

Instead, the biggest takeaway was that there is no checklist.

Hold on - I know you want something tangible, it’s coming - stay with me.

The assumption I hadn’t questioned

The facilitator challenged a belief I hadn’t questioned before: we often talk about neurodiversity as if it describes a group of people.

The workshop argued that neurodiversity is the natural variation in how humans think, focus, process information and communicate.

That reframing changes the problem entirely.

Why this matters for design

When we think in categories, we tend to design for ourselves and then add accommodations afterwards. We build the workshop, the meeting, the presentation or the product, based on our own preferences and then ask, “now how do we make this accessible?”

When we think in variation, we start by accepting that people will experience the same thing differently.

The workshop wasn’t really about fonts or slide templates. It was about design choices.

How much information do you put on a slide?

Do people know why they’re learning something?

Can they contribute in different ways?

Have you considered sensory load, attention span, or processing time?

A familiar product challenge

As a product person, the parallel felt familiar: even if you start with the customer, there’s still a risk of designing for how something is assumed to be experienced, rather than how it actually is - a gap that only closes with context and testing.

Whether you’re designing software, a workshop, a conference talk or a team meeting, the principle feels surprisingly similar:

Start with the expectation that people will experience the same thing differently. Design from there.