Arthur
@schmidtpabst.bsky.social
Systems-oriented designer.
UI/UX, workflows, AI-assisted tools.
Making complex things usable. Berlin.
UI/UX, workflows, AI-assisted tools.
Making complex things usable. Berlin.
Systems design is slower upfront.
But it saves weeks later;
especially once real users enter the picture.
But it saves weeks later;
especially once real users enter the picture.
January 26, 2026 at 9:42 AM
Systems design is slower upfront.
But it saves weeks later;
especially once real users enter the picture.
But it saves weeks later;
especially once real users enter the picture.
AI accelerates structure.
Humans provide meaning.
My job sits in between:
framing, shaping, deciding what _should_ exist.
Humans provide meaning.
My job sits in between:
framing, shaping, deciding what _should_ exist.
January 26, 2026 at 9:38 AM
AI accelerates structure.
Humans provide meaning.
My job sits in between:
framing, shaping, deciding what _should_ exist.
Humans provide meaning.
My job sits in between:
framing, shaping, deciding what _should_ exist.
To me: AI is most useful when it removes friction,
not when it replaces judgment.
Curious how others are structuring their workflows around that.
not when it replaces judgment.
Curious how others are structuring their workflows around that.
January 22, 2026 at 7:18 AM
To me: AI is most useful when it removes friction,
not when it replaces judgment.
Curious how others are structuring their workflows around that.
not when it replaces judgment.
Curious how others are structuring their workflows around that.
I recently created: Context. A place to read AI dialectically, not optimistically or catastrophically.
context.schmidtpabst.com
context.schmidtpabst.com
January 22, 2026 at 7:16 AM
I recently created: Context. A place to read AI dialectically, not optimistically or catastrophically.
context.schmidtpabst.com
context.schmidtpabst.com
People don’t interact with features.
They interact with **systems over time**.
That’s why I focus on workflows, documentation, and structure;
not just screens.
They interact with **systems over time**.
That’s why I focus on workflows, documentation, and structure;
not just screens.
January 22, 2026 at 7:14 AM
People don’t interact with features.
They interact with **systems over time**.
That’s why I focus on workflows, documentation, and structure;
not just screens.
They interact with **systems over time**.
That’s why I focus on workflows, documentation, and structure;
not just screens.
I started Context because most AI discourse felt too loud, too binary, or too confident.
context.schmidtpabst.com
context.schmidtpabst.com
January 21, 2026 at 9:44 AM
I started Context because most AI discourse felt too loud, too binary, or too confident.
context.schmidtpabst.com
context.schmidtpabst.com
I don’t decorate interfaces.
I design **behavior**, **flows**, and **decision paths**;
then give them a visual language that makes sense emotionally.
I design **behavior**, **flows**, and **decision paths**;
then give them a visual language that makes sense emotionally.
January 21, 2026 at 9:40 AM
I don’t decorate interfaces.
I design **behavior**, **flows**, and **decision paths**;
then give them a visual language that makes sense emotionally.
I design **behavior**, **flows**, and **decision paths**;
then give them a visual language that makes sense emotionally.
Designers keep being asked to “make it pretty.”
The harder part is making systems understandable, adaptable, and humane.
That’s the work I care about.
The harder part is making systems understandable, adaptable, and humane.
That’s the work I care about.
January 19, 2026 at 9:05 AM
Designers keep being asked to “make it pretty.”
The harder part is making systems understandable, adaptable, and humane.
That’s the work I care about.
The harder part is making systems understandable, adaptable, and humane.
That’s the work I care about.
“Technical” and “emotional” are not opposites.
They’re coupled variables.
Change one, the other reacts.
Designing without that awareness is how bad systems happen.
They’re coupled variables.
Change one, the other reacts.
Designing without that awareness is how bad systems happen.
January 19, 2026 at 9:03 AM
“Technical” and “emotional” are not opposites.
They’re coupled variables.
Change one, the other reacts.
Designing without that awareness is how bad systems happen.
They’re coupled variables.
Change one, the other reacts.
Designing without that awareness is how bad systems happen.
Code already shapes emotions.
Interfaces frustrate, calm, confuse, empower.
I design systems with that in mind:
structure first, aesthetics as consequence.
Interfaces frustrate, calm, confuse, empower.
I design systems with that in mind:
structure first, aesthetics as consequence.
January 16, 2026 at 6:39 AM
Code already shapes emotions.
Interfaces frustrate, calm, confuse, empower.
I design systems with that in mind:
structure first, aesthetics as consequence.
Interfaces frustrate, calm, confuse, empower.
I design systems with that in mind:
structure first, aesthetics as consequence.
If your product feels:
• powerful but overwhelming
• flexible but fragile
• elegant but hard to maintain
That’s usually a systems issue, not a visual one.
• powerful but overwhelming
• flexible but fragile
• elegant but hard to maintain
That’s usually a systems issue, not a visual one.
January 16, 2026 at 6:38 AM
If your product feels:
• powerful but overwhelming
• flexible but fragile
• elegant but hard to maintain
That’s usually a systems issue, not a visual one.
• powerful but overwhelming
• flexible but fragile
• elegant but hard to maintain
That’s usually a systems issue, not a visual one.
I work at the intersection of code and emotion.
Not code _or_ emotion.
Not tech _versus_ art.
The interesting work happens where systems shape how people _feel_.
Not code _or_ emotion.
Not tech _versus_ art.
The interesting work happens where systems shape how people _feel_.
January 15, 2026 at 6:58 AM
I work at the intersection of code and emotion.
Not code _or_ emotion.
Not tech _versus_ art.
The interesting work happens where systems shape how people _feel_.
Not code _or_ emotion.
Not tech _versus_ art.
The interesting work happens where systems shape how people _feel_.
I don’t really design “projects.”
I design orientation:
ways for people to stay emotionally and cognitively grounded inside complex systems.
That’s the thread across everything I do.
I design orientation:
ways for people to stay emotionally and cognitively grounded inside complex systems.
That’s the thread across everything I do.
January 14, 2026 at 5:53 AM
I don’t really design “projects.”
I design orientation:
ways for people to stay emotionally and cognitively grounded inside complex systems.
That’s the thread across everything I do.
I design orientation:
ways for people to stay emotionally and cognitively grounded inside complex systems.
That’s the thread across everything I do.
The always admirable Moxie Marlinspike released a fully encrypted LLM! I just read about it on @arstechnica.com
It's called: confer.to
I will give it a whirl ASAP. Did you already?
It's called: confer.to
I will give it a whirl ASAP. Did you already?
Confer
Confer - Private AI
confer.to
January 14, 2026 at 5:39 AM
The always admirable Moxie Marlinspike released a fully encrypted LLM! I just read about it on @arstechnica.com
It's called: confer.to
I will give it a whirl ASAP. Did you already?
It's called: confer.to
I will give it a whirl ASAP. Did you already?
Here to exchange notes, share process, and collaborate.
Interested in design systems, AI in creative work, and making complex things usable.
If that overlaps: hello 👋
Interested in design systems, AI in creative work, and making complex things usable.
If that overlaps: hello 👋
January 13, 2026 at 8:24 AM
Here to exchange notes, share process, and collaborate.
Interested in design systems, AI in creative work, and making complex things usable.
If that overlaps: hello 👋
Interested in design systems, AI in creative work, and making complex things usable.
If that overlaps: hello 👋
My work usually involves:
• systems & workflow design
• UI/UX for web and tools
• information architecture
• visual languages
• AI-assisted creative processes
If your tools feel powerful but confusing, that’s my entry point.
• systems & workflow design
• UI/UX for web and tools
• information architecture
• visual languages
• AI-assisted creative processes
If your tools feel powerful but confusing, that’s my entry point.
January 13, 2026 at 8:23 AM
My work usually involves:
• systems & workflow design
• UI/UX for web and tools
• information architecture
• visual languages
• AI-assisted creative processes
If your tools feel powerful but confusing, that’s my entry point.
• systems & workflow design
• UI/UX for web and tools
• information architecture
• visual languages
• AI-assisted creative processes
If your tools feel powerful but confusing, that’s my entry point.
AI didn’t replace my work.
It changed where my attention goes.
Less execution.
More framing, structuring, and deciding what matters.
It changed where my attention goes.
Less execution.
More framing, structuring, and deciding what matters.
January 13, 2026 at 8:23 AM
AI didn’t replace my work.
It changed where my attention goes.
Less execution.
More framing, structuring, and deciding what matters.
It changed where my attention goes.
Less execution.
More framing, structuring, and deciding what matters.
I’m a systems-oriented designer.
I work between visuals, code, and narrative; designing workflows, interfaces, and structures that make complex tech usable.
Currently building and documenting AI-assisted design systems from Berlin.
I work between visuals, code, and narrative; designing workflows, interfaces, and structures that make complex tech usable.
Currently building and documenting AI-assisted design systems from Berlin.
January 13, 2026 at 8:23 AM
I’m a systems-oriented designer.
I work between visuals, code, and narrative; designing workflows, interfaces, and structures that make complex tech usable.
Currently building and documenting AI-assisted design systems from Berlin.
I work between visuals, code, and narrative; designing workflows, interfaces, and structures that make complex tech usable.
Currently building and documenting AI-assisted design systems from Berlin.