UDSKRIFT 🔗
1
00:00:00,000 --> 00:00:02,908
Today we're diving into how
complexity accumulates in
2
00:00:02,908 --> 00:00:06,146
systems through a series of
small, locally rational choices
3
00:00:06,146 --> 00:00:09,275
that lead to fragility and
incomprehensibility over time.
4
00:00:09,275 --> 00:00:12,348
And on the community front,
designers are asking whether
5
00:00:12,348 --> 00:00:15,751
honest portfolios are costing
them jobs, and what happens when
6
00:00:15,751 --> 00:00:17,751
your entire craft goes on
autopilot.
7
00:00:21,727 --> 00:00:24,433
Welcome to The Feed and The
Thread, brought to you by
8
00:00:24,433 --> 00:00:27,649
Chicago Camps. Our next UX Camp
event is coming up on Saturday,
9
00:00:27,649 --> 00:00:30,764
May 30th. Tickets are free -
with an option to pay if it's in
10
00:00:30,764 --> 00:00:34,032
budget for you. There's an open
call for speakers so now is your
11
00:00:34,032 --> 00:00:37,248
chance to get on stage and share
your ideas! You can also find
12
00:00:37,248 --> 00:00:40,210
The Feed & The Thread online at
feed and thread dot com to
13
00:00:40,210 --> 00:00:43,273
submit your feeds, or download
our app for all the feeds and
14
00:00:43,273 --> 00:00:45,273
threads delivered right to your
pocket.
15
00:00:52,564 --> 00:00:55,919
The industry's been busy over
the past day. Here's what's
16
00:00:55,919 --> 00:00:59,391
catching our attention and
worthy of yours. In a new piece
17
00:00:59,391 --> 00:01:02,569
titled "How complexity
accumulates," Michael Parent at
18
00:01:02,569 --> 00:01:05,629
UX Design.cc explores how
systems become fragile and
19
00:01:05,629 --> 00:01:09,042
unmaintainable through small,
locally rational choices. He
20
00:01:09,042 --> 00:01:12,279
notes that each addition
multiplies rather than adds to
21
00:01:12,279 --> 00:01:16,104
the overall system's complexity,
emphasizing the need for Systems
22
00:01:16,104 --> 00:01:19,870
Thinking in managing this issue.
Jeff Sauro, PhD, and Jim Lewis,
23
00:01:19,870 --> 00:01:23,225
PhD at MeasuringU introduce
Bayesian thinking as a method
24
00:01:23,225 --> 00:01:26,814
for updating beliefs about user
experience based on collected
25
00:01:26,814 --> 00:01:30,110
data in, "An Intro to Bayesian
Thinking for UX Research:
26
00:01:30,110 --> 00:01:33,464
Updating Beliefs with Data."
They illustrate this through
27
00:01:33,464 --> 00:01:36,642
examples like estimating
completion rates in usability
28
00:01:36,642 --> 00:01:39,820
tests. Also publishing
recently: Codrops, CSS-Tricks,
29
00:01:39,820 --> 00:01:43,056
and UX Planet. Be sure to check
them out in your feeds!
30
00:01:50,356 --> 00:01:52,811
Okay, what's the community
buzzing about?
31
00:01:52,811 --> 00:01:56,402
Over in r/UXDesign, a designer
asked a question that clearly
32
00:01:56,402 --> 00:01:59,754
struck a chord: is honesty
killing my portfolio? They've
33
00:01:59,754 --> 00:02:03,286
been getting rejected because
their case studies don't have
34
00:02:03,286 --> 00:02:06,937
the polished research artifacts
and process diagrams, but the
35
00:02:06,937 --> 00:02:10,349
thing is, their real projects
didn't allow for those. The
36
00:02:10,349 --> 00:02:14,240
community's take? Don't hide the
constraints; show how you worked
37
00:02:14,240 --> 00:02:17,413
within them. Navigating
limitations is its own design
38
00:02:17,413 --> 00:02:20,884
skill, and a portfolio that
shows that is more honest than
39
00:02:20,884 --> 00:02:23,997
one full of made-up
deliverables. And sticking with
40
00:02:23,997 --> 00:02:27,768
r/UXDesign, there's a confession
thread that's worth your time:
41
00:02:27,768 --> 00:02:31,240
when did your craft turn into
autopilot? One designer said
42
00:02:31,240 --> 00:02:35,011
they ran an entire design cycle
and felt absolutely nothing. No
43
00:02:35,011 --> 00:02:38,782
curiosity, no investment, just
muscle memory. The advice coming
44
00:02:38,782 --> 00:02:42,673
in is to find that one moment in
your workflow where you can stop
45
00:02:42,673 --> 00:02:46,324
and ask "why" instead of just
"what's next." Small thing, but
46
00:02:46,324 --> 00:02:50,215
it snaps you back into the work.
Meanwhile, over at r/web_design,
47
00:02:50,215 --> 00:02:53,807
the comments are going on a
thread asking whether AI website
48
00:02:53,807 --> 00:02:57,518
builders are ready to replace
WordPress. The consensus so far:
49
00:02:57,518 --> 00:03:01,229
they're fast for a first draft,
but when it comes to long-term
50
00:03:01,229 --> 00:03:04,222
maintenance and client
reliability, most folks are
51
00:03:04,222 --> 00:03:07,873
sticking with what they know.
Speed to launch is great; speed
52
00:03:07,873 --> 00:03:11,645
to headache is not. That's what
folks are buzzing about today!
53
00:03:18,944 --> 00:03:22,018
Chicago Camps is hosting UX Camp
Summer on Saturday, May 30th.
54
00:03:22,018 --> 00:03:24,646
There's an open call for
speakers so submit your idea
55
00:03:24,646 --> 00:03:27,670
today! It's an online event, so
you can join from anywhere in
56
00:03:27,670 --> 00:03:30,744
the world! Tickets are free,
thanks to the generosity of the
57
00:03:30,744 --> 00:03:33,570
community! If it's within your
budget, you can purchase a
58
00:03:33,570 --> 00:03:36,545
general admission ticket for
only thirteen dollars and fifty
59
00:03:36,545 --> 00:03:38,974
cents. Get tickets now at
Chicago Camps dot org.
60
00:03:46,275 --> 00:03:49,022
Today, we talked about how
complexity accumulates in
61
00:03:49,022 --> 00:03:52,245
systems, highlighting the need
for Systems Thinking. And over
62
00:03:52,245 --> 00:03:55,626
in the community, the portfolio
honesty thread really stood out:
63
00:03:55,626 --> 00:03:58,691
the idea that showing how you
worked within constraints is
64
00:03:58,691 --> 00:04:01,596
itself a design skill and that
shouldn't be overlooked.
65
00:04:01,596 --> 00:04:04,133
That's your update for today.
See you next time.
66
00:04:04,633 --> 00:04:08,107
That's The Feed and The Thread
for today. Keep designing with
67
00:04:08,107 --> 00:04:10,107
intention!