TRANSCRIPT 🔗
WEBVTT
NOTE
This file was generated by Descript
00:00:04.103 --> 00:00:06.893
Jonny: Hi, welcome to another
episode of the Near Future
00:00:07.083 --> 00:00:08.203
Podcast with Tom and Jonny.
00:00:08.603 --> 00:00:11.553
We've got a lot on the docket this week,
so we're gonna get straight into it.
00:00:12.493 --> 00:00:15.013
first of all, Tom, you ran
another Mostly Working event
00:00:15.023 --> 00:00:17.983
with Kate Pincot from Multiverse.
00:00:18.563 --> 00:00:20.263
Wonder if you wanna tell us a
little bit about that upfront?
00:00:21.701 --> 00:00:21.971
Tom: yeah.
00:00:21.971 --> 00:00:23.021
It was, super fun.
00:00:23.031 --> 00:00:28.681
Ran that last week, from the
Gradient Labs office in London,
00:00:28.901 --> 00:00:30.801
and we had a great crowd.
00:00:30.801 --> 00:00:32.671
Thanks to anyone who's listening
to this who came along.
00:00:33.431 --> 00:00:34.211
was a great speaker.
00:00:34.671 --> 00:00:37.441
gave some really interesting insights
into how Multiverse are thinking
00:00:37.441 --> 00:00:44.971
about the opportunity for, design
to scale their approach and impact
00:00:44.981 --> 00:00:51.061
through tooling and agents to
scale the, their brand is applied.
00:00:51.121 --> 00:00:51.821
It was very cool.
00:00:52.383 --> 00:00:52.813
Jonny: Nice
00:00:52.861 --> 00:00:56.611
Tom: also just got a call out at the
start, Jonny, that you, the last time
00:00:56.611 --> 00:00:59.211
we recorded there was a reversing truck,
and this time it sounds like there's
00:00:59.995 --> 00:01:00.545
Jonny: There's a power saw?
00:01:00.835 --> 00:01:01.435
Yeah, I'm gonna turn-
00:01:01.601 --> 00:01:03.751
Tom: saw, angle grinder.
00:01:04.941 --> 00:01:07.841
I think it really enhances
the ambiance though,
00:01:07.935 --> 00:01:10.775
Jonny: Makes it feel real,
We're, th-this is the real world.
00:01:10.775 --> 00:01:12.765
We're not, we don't exist in a vacuum.
00:01:13.135 --> 00:01:13.385
We're not AI
00:01:13.513 --> 00:01:13.643
Tom: this
00:01:13.795 --> 00:01:14.585
Jonny: from space.
00:01:16.623 --> 00:01:17.093
Tom: Yes.
00:01:17.173 --> 00:01:18.043
Not, at least not yet.
00:01:18.527 --> 00:01:21.387
Jonny: We're not Synthesia
models and ElevenLabs voices.
00:01:22.105 --> 00:01:22.355
Tom: It
00:01:24.905 --> 00:01:27.155
although I wonder if there's
an Eleven Lan- Labs reversing
00:01:27.185 --> 00:01:28.685
truck that we can add on to our
00:01:29.013 --> 00:01:29.513
Jonny: Probably.
00:01:29.555 --> 00:01:30.065
Tom: in the future.
00:01:30.443 --> 00:01:30.703
Jonny: Yeah.
00:01:31.075 --> 00:01:33.105
Tom: anyway, Mostly Working
last week was great with Kate.
00:01:33.855 --> 00:01:39.395
it was, really fascinating to hear
the approach there, and, just great
00:01:39.395 --> 00:01:42.885
to host it in a new space and,
be surrounded by great people.
00:01:43.765 --> 00:01:47.065
the other thing to just share up
front is that we're gearing up to
00:01:47.115 --> 00:01:50.905
welcome our first podcast guest
Load full transcript
next
week, or we will be recording with
00:01:50.905 --> 00:01:53.645
our first guest next week, and we
have guests lined up throughout July.
00:01:54.505 --> 00:02:00.015
really excited for this next chapter
of exploring with this podcast.
00:02:00.235 --> 00:02:02.525
So if you're listening to this and
have any feedback that would help us
00:02:02.525 --> 00:02:06.155
not make a fool of ourselves when we
invite real important people on to
00:02:06.155 --> 00:02:07.515
speak with us, please let us know.
00:02:08.697 --> 00:02:08.987
Jonny: Awesome.
00:02:09.157 --> 00:02:12.167
I also have a bit of news up front,
Tom, which is that I'm standing up.
00:02:13.671 --> 00:02:13.931
Tom: yeah
00:02:15.167 --> 00:02:20.677
Jonny: I ran one podcast in a prior
life, in a prior company, and podcasts
00:02:20.687 --> 00:02:24.947
then you could just do audio, and you
could be lounging around or staring
00:02:24.947 --> 00:02:28.277
into space or picking your nose,
and it would be absolutely fine.
00:02:28.967 --> 00:02:32.627
And now you have to do video, and I
feel like I'm getting found out here.
00:02:32.657 --> 00:02:35.952
I watched-- or I edited the last
episode, and I was like, "What
00:02:35.952 --> 00:02:37.137
are you doing with yourself?"
00:02:37.137 --> 00:02:42.117
So my focus is now on standing
still, looking at the camera.
00:02:42.647 --> 00:02:46.997
And so if anyone's listening to this and
not watching it, it was still not gonna
00:02:46.997 --> 00:02:48.687
be great, so I wouldn't tune in quite yet.
00:02:48.687 --> 00:02:50.417
But maybe in a year's
time I'll be good at this.
00:02:52.037 --> 00:02:56.357
but yeah, the, sunglasses last
week was an interesting option.
00:02:56.847 --> 00:03:00.797
I feel like, this week may be a
little bit better, but we'll see.
00:03:01.217 --> 00:03:06.547
I, just wanted to ask you before we go
into the, main bulk of the, podcast,
00:03:07.177 --> 00:03:10.637
you just mentioned Mostly Working,
but you've had some reflections
00:03:10.637 --> 00:03:11.997
on Mostly Working as a format.
00:03:12.027 --> 00:03:16.407
Running a meetup is hard, working out
how to make it work in person and remote.
00:03:16.877 --> 00:03:20.877
Just, for those people that may have
been to Mostly Working, which may be
00:03:20.877 --> 00:03:25.497
some of our listeners at the moment,
just, yeah, like what you're learning
00:03:25.497 --> 00:03:28.517
so far I think is interesting for
those people thinking about, "I'd
00:03:28.517 --> 00:03:30.947
love to, to run a meetup or an event."
00:03:31.859 --> 00:03:32.829
Tom: Yeah, of course.
00:03:33.839 --> 00:03:37.929
So we've done five now, and they've
been roughly every month since January.
00:03:38.599 --> 00:03:44.489
I think the meta reflection is that
when we started in January, the, state
00:03:44.489 --> 00:03:48.799
of the world was that people were
aware of AI but hadn't really spent a
00:03:48.799 --> 00:03:50.389
ton of time building with these tools.
00:03:51.169
--> 00:03:53.599
And six months later, is very different.
00:03:53.749 --> 00:03:58.259
Most people have been trying, exploring,
playing with these things a little bit.
00:03:59.259 --> 00:04:02.209
there's still a gap between
playing with something and actually
00:04:02.209 --> 00:04:03.249
getting real value from it.
00:04:03.689 --> 00:04:09.999
But the need to have a dedicated space
to get hands-on and build things,
00:04:10.879 --> 00:04:15.509
to have evolved from just trying
something through to actually getting--
00:04:15.519 --> 00:04:16.569
doing something useful with it.
00:04:17.299 --> 00:04:19.649
which I think is, as an
interesting reflection of
00:04:19.649 --> 00:04:21.259
where we are with AI right now.
00:04:22.179 --> 00:04:22.759
And I think
00:04:23.291 --> 00:04:24.471
Jonny: Oh, seamless transition.
00:04:25.689 --> 00:04:26.019
Tom: yeah,
00:04:26.091 --> 00:04:27.001
Jonny: that was so seamless
00:04:28.739 --> 00:04:30.909
Tom: it, would be if I carried on,
but there's another thing I wanted to
00:04:30.949 --> 00:04:36.409
mention, which is that, I think that
this, the, the-- So when we started
00:04:36.459 --> 00:04:39.749
running these events, it was a really
wide spread of what people were interested
00:04:39.749 --> 00:04:44.069
in hearing about from opening the
terminal for the first time and starting
00:04:44.069 --> 00:04:45.119
to use Claude Code for the first time.
00:04:45.119 --> 00:04:49.479
And we had various designers coming
through who did open Claude Code for
00:04:49.479 --> 00:04:55.189
the first time or Cursor or whatever
the tool was, in those sessions.
00:04:55.631 --> 00:04:55.951
Jonny: Yeah
00:04:56.019 --> 00:05:00.339
Tom: they came back a month later
and said, "Wow, I've got so far.
00:05:00.399 --> 00:05:01.409
I built so much stuff.
00:05:01.569 --> 00:05:05.109
I have now have product that I've shared
with my internal team and they're all
00:05:05.109 --> 00:05:08.989
using it and working off of it now," or,
"I'm starting to speak with VCs about
00:05:08.989 --> 00:05:13.309
raising money for this tool that I've l-
built for the first time a month ago."
00:05:14.319 --> 00:05:16.959
so it's very inspiring to, to, hear that.
00:05:17.209 --> 00:05:21.649
But I think the, level of conversation
has shifted at this point towards
00:05:22.099 --> 00:05:26.979
designers generally being a bit more
curious about actual applied ways of
00:05:26.979 --> 00:05:29.059
working inside companies at scale.
00:05:29.389 --> 00:05:33.729
So less one-off experiments or people
starting from scratch in their own
00:05:35.219 --> 00:05:40.349
design system constraint legacy
product free world through to how
00:05:40.349 --> 00:05:45.639
do we actually make this work inside
our team of five or 10 or 20 or 100.
00:05:45.639 --> 00:05:51.169
And, and I think there's a level
of there that means that some,
00:05:53.779 --> 00:05:56.279
some ways companies are
approaching this are very unique
00:05:56.299 --> 00:05:57.599
to how that company operates.
00:05:58.767 --> 00:05:59.077
Jonny: Yeah
00:05:59.169 --> 00:06:01.469
Tom: if your team is five people,
it might be a bit different because
00:06:01.469 --> 00:06:04.269
of the scale and size and the kind
of challenges you need to tackle.
00:06:05.039 --> 00:06:05.359
Jonny: Yeah
00:06:05.589 --> 00:06:08.609
Tom: to get a, glimpse into like how
real people are working with these
00:06:08.609 --> 00:06:13.319
tools in real settings, not just the
sort of sandboxed, I'm gonna prototype
00:06:13.319 --> 00:06:14.759
something on my own version of that.
00:06:15.719 --> 00:06:22.349
Jonny: I think that we are past the,
cool demo in my bedroom, local host,
00:06:23.029 --> 00:06:26.729
isn't this, an interesting technology
and let's see how far it can go stage.
00:06:27.189 --> 00:06:32.479
And companies are looking at their token
costs, but also teams are saying: all
00:06:32.479 --> 00:06:33.929
of this promise, what's it turning into?
00:06:33.929 --> 00:06:35.359
Is it turning into actual value?
00:06:35.909 --> 00:06:39.599
And, so now this is good though,
because we've moved out of this
00:06:39.629 --> 00:06:43.589
existential fear and, oh my God,
maybe it can do everything, maybe
00:06:43.589 --> 00:06:46.089
we're cooked, to this is a tool.
00:06:46.699 --> 00:06:49.789
We can't work out how to use it
well together yet, so let's do that.
00:06:49.989 --> 00:06:54.229
And I think, I haven't been to-- I
wasn't at this latest Mostly Working,
00:06:54.229 --> 00:06:59.409
but the conversation then matures into,
practically how do we shape this into
00:06:59.409 --> 00:07:02.269
something that I can take back to my
team and everyone will be like, "Great,
00:07:02.289 --> 00:07:06.219
this is genuinely useful," rather
than, "That's a cool side project.
00:07:06.759 --> 00:07:11.389
Let's get back to drawing
rectangles," or whatever it is.
00:07:12.589 --> 00:07:13.139
Tom: Exactly.
00:07:13.149 --> 00:07:17.789
So with that perfect transition, let's
talk about config, Figma Config, 'cause
00:07:17.789 --> 00:07:23.049
that happened at the end of last week,
and, Figma, a tool historically known
00:07:23.049 --> 00:07:27.509
for being great at drawing rectangles,
now exploring a bunch of new things.
00:07:27.879 --> 00:07:34.849
they released a bunch of new features
from motion to the code layer to, various
00:07:34.919 --> 00:07:41.889
other, smorgasbord of functionality
that they're, hinting at and releasing.
00:07:43.019 --> 00:07:46.289
an interesting set of things
for us to be exploring.
00:07:46.819 --> 00:07:50.389
Jonny and I have Weren't there in
person, so we can't speak to the
00:07:50.389 --> 00:07:53.719
sort of what the vibe was like in
the room, but we've had some thoughts
00:07:53.719 --> 00:07:54.959
and reflections following it.
00:07:55.699 --> 00:07:58.529
Jonny, do you want to k- kick
us off with a conversation
00:07:58.529 --> 00:07:59.839
around config and what's next
00:07:59.881
--> 00:08:00.221
Jonny: Sure
00:08:00.329 --> 00:08:01.329
Tom: in the tooling space?
00:08:01.791 --> 00:08:04.211
Jonny: Yeah, hot takes from across
the Atlantic coming your way.
00:08:05.551 --> 00:08:09.981
yeah, what's-- So people who've read my
blog in the past and seen what I've been
00:08:09.981 --> 00:08:13.481
writing could take me as a Figma hater.
00:08:14.201 --> 00:08:18.631
That is not true, although I've always
felt that Figma and the tools that
00:08:18.961 --> 00:08:24.571
predate Figma, Sketch and, I, drew
my first UI in Photoshop probably.
00:08:24.871 --> 00:08:31.561
But they don't-- They're, a, bad
facsimile of the real thing, and at
00:08:31.571 --> 00:08:35.971
best, they can achieve a percentage,
not much more than 50% of the fidelity
00:08:35.971 --> 00:08:39.511
of something that is actually built in
the technology that it will end up being
00:08:39.511 --> 00:08:44.421
in, whether that's in Swift or whether
that's in the web or whatever it is.
00:08:45.241 --> 00:08:50.321
And I have also personally found as a
designer that has coded for a long time,
00:08:50.421 --> 00:08:58.111
that the sort of rote work involved in
drawing rectangles and, Figma have now
00:08:58.111 --> 00:09:02.341
released slots, which for people that are
in this world will know what that means.
00:09:02.341 --> 00:09:06.561
But, a big time saver, but it's amazing
that it took them so long to do that.
00:09:06.571 --> 00:09:10.031
That feels like the actual biggest
release of the year, in many ways.
00:09:10.731 --> 00:09:14.551
but it's like really time-consuming
to get to something that in code you
00:09:14.551 --> 00:09:18.201
could get to very quickly, even before
AI, because I could have a blob of data
00:09:18.201 --> 00:09:21.921
and just repeat that data to create
a table and et cetera, et cetera.
00:09:21.981 --> 00:09:24.301
Anyway, so I'm not a Figma hater.
00:09:24.741 --> 00:09:28.491
It's come from a place that
made complete sense, I think,
00:09:28.521 --> 00:09:30.741
up until coding models appeared.
00:09:32.171 --> 00:09:37.051
And they are very bound to their
architecture and their way of
00:09:37.051 --> 00:09:40.121
working and the workflows that they
have been selling for, many years.
00:09:40.991 --> 00:09:46.441
And I think that what in the features
they're releasing now is effectively
00:09:46.441 --> 00:09:50.261
trying to protect the golden goose,
which is what they currently have,
00:09:50.301 --> 00:09:54.951
while also reaching into some of the
other aspects of the design process
00:09:55.011 --> 00:10:01.711
that they have no-- haven't been
able to service, up until this point.
00:10:02.091 --> 00:10:03.471
So they've gone in both directions.
00:10:03.781 --> 00:10:09.831
On one side, which is the more
creative, like image making and
00:10:10.581 --> 00:10:15.951
what could this be and, th-that like
earliest stage of the design process.
00:10:16.351 --> 00:10:19.351
They've built Motion, which is
their sort of After
Effects,
00:10:19.531 --> 00:10:22.131
Lottie type tool for motion stuff.
00:10:23.041 --> 00:10:27.181
and they bought a company, Weavy,
which they've turned into Figma Weave,
00:10:27.181 --> 00:10:29.601
which is like asset generation with AI.
00:10:30.441 --> 00:10:34.781
Both interesting things and feel like a
good fit probably if you think of Figma
00:10:34.781 --> 00:10:37.681
as a tool where you start doing your
work and imagine what it could look like.
00:10:39.111 --> 00:10:41.691
and then they've built in the other
direction fairly consistently.
00:10:41.691 --> 00:10:46.511
They've built Figma Sites and,
and, Figma Make, which was
00:10:46.511 --> 00:10:48.101
their sort of vibe coding thing.
00:10:48.111 --> 00:10:52.181
That was last year, and now they
have built these code components
00:10:52.181 --> 00:10:56.581
within Figma, where you can drop
code blocks into your Figma canvas.
00:10:57.971 --> 00:11:01.883
And haven't tried it because it's
not available yet So we can only
00:11:01.883 --> 00:11:03.333
go by what they've announced.
00:11:04.183 --> 00:11:09.643
But it sort of-- it does slightly feel
like forcing code into the canvas, which
00:11:09.643 --> 00:11:10.883
still feels like the wrong way around.
00:11:12.333 --> 00:11:16.243
if the source of truth is code, why
am I putting the source of truth into
00:11:16.243 --> 00:11:18.523
something that isn't the source of
truth just to push it back again?
00:11:18.523 --> 00:11:22.003
It feels of course, Figma-- that's
how Figma should do it because they
00:11:22.003 --> 00:11:24.443
need to keep people in their canvas.
00:11:24.813 --> 00:11:27.523
But it doesn't feel like if you were
to design something from scratch,
00:11:27.523 --> 00:11:28.533
that's how you would do it today.
00:11:28.533 --> 00:11:33.593
So that's a long way of saying it feels
like a bit of a mess and a bit of like
00:11:33.623 --> 00:11:38.353
grabbing all the sort of bits of the, the
design process that they haven't touched
00:11:38.353 --> 00:11:43.003
yet and trying to do a bit of an Adobe
on it and scoop up all of those existing
00:11:43.483 --> 00:11:46.693
enterprise contracts and make sure that
they don't wander off because they have
00:11:46.693 --> 00:11:51.263
something good enough in the existing
r-relationship they have with Figma.
00:11:53.463 --> 00:11:55.803
I don't know if that sounds
really negative orâ¦
00:11:55.943 --> 00:12:02.363
But I think, what-- the one thing I
did come out with was none of this
00:12:02.363 --> 00:12:06.733
feels like the thing that solidifies
Figma's place in the design universe.
00:12:07.433 --> 00:12:09.943
it's good for people that
want to stick to Figma.
00:12:10.863 --> 00:12:14.433
I think a lot of these features
will be underbaked for a while yet.
00:12:15.343 --> 00:12:19.383
So if you want best in class at,
for example, designing in code, you
00:12:19.383 --> 00:12:20.833
probably wouldn't use Figma for that.
00:12:21.173 --> 00:12:24.383
If you want
to design in code a bit
while you mainly stay in your canvas,
00:12:24.623 --> 00:12:26.963
it makes sense to have-- to, use Figma.
00:12:27.353 --> 00:12:30.443
But as they start to move into these
things that they're historically less
00:12:30.443 --> 00:12:34.513
good at and less geared up to be good
at, I think it weakens their position
00:12:34.513 --> 00:12:37.803
generally in the market, would be my, bet.
00:12:39.263 --> 00:12:41.943
and I'm talking my book because I
wrote an article in February about
00:12:41.943 --> 00:12:46.063
this, and I still believe it to
be true, that the s- the source
00:12:46.063 --> 00:12:47.883
of truth is the ultimate question.
00:12:47.893 --> 00:12:51.093
Like, where does this all
ladder up to or down to?
00:12:51.953 --> 00:12:52.653
Where are the,
00:12:54.913 --> 00:13:01.953
the core components, quite literally
or figuratively, of the design process,
00:13:02.183 --> 00:13:05.526
where do they live and where's the
truth that sits underneath all of those,
00:13:05.526 --> 00:13:09.543
whether that's a design system or the
actual code base or things like that.
00:13:10.383 --> 00:13:15.643
and that probably points the direction
to where the future is, I posit.
00:13:16.653 --> 00:13:19.133
and what that means, I think, for a
lot of other tools that have sprung
00:13:19.133 --> 00:13:25.613
up, and I've built a website to capture
a, big list of them, designtools.fyi.
00:13:25.643 --> 00:13:26.423
I'll plug it again.
00:13:27.093 --> 00:13:31.413
but, I think a lot of those tools
will look at this and say, "We
00:13:31.413 --> 00:13:33.443
probably expected Figma to, do this."
00:13:33.923 --> 00:13:37.523
And some of those have made a bet,
which is one part of what Figma's now
00:13:37.523 --> 00:13:39.263
shipped, and probably they'd be worried.
00:13:39.633 --> 00:13:45.383
But those tools that are building on code
as source of truth, I think can feel like
00:13:45.733 --> 00:13:47.463
this doesn't invalidate what we're doing.
00:13:47.463 --> 00:13:51.033
This is what Figma should be doing
for them, but we can do something
00:13:51.033 --> 00:13:53.433
different, and there'll be enough
people in the world that will want
00:13:53.433 --> 00:13:55.293
that, that we can feel confident in it.
00:13:56.083 --> 00:13:59.183
so mainly choice is still alive.
00:13:59.833 --> 00:14:02.873
You can still use Figma, and that's
great, and for a lot of teams,
00:14:02.873 --> 00:14:04.163
that's the right move right now.
00:14:05.003 --> 00:14:10.573
but it doesn't remove any of the other
exciting, often open source or really
00:14:10.593 --> 00:14:14.823
interesting projects that are happening
to explore new ways of designing and more
00:14:14.823 --> 00:14:16.203
sort of modern ways of designing as well.
00:14:16.363 --> 00:14:19.603
So I talked for a little
while, but there we go.
00:14:21.303 --> 00:14:22.423
yeah, what, do you think, Tom?
00:14:23.303 --> 00:14:26.763
Tom: I th-- Y- yeah, I th-- just to
play back some of the sort of themes I'm
00:14:26.763 --> 00:14:35.397
hearing from you, The design process is,
I think for a while, Figma has owned the
00:14:35.407 --> 00:14:42.207
entire design process as a function, as a
discipline, and that process is starting
00:14:42.207 --> 00:14:45.417
to be pulled in two different directions.
00:14:45.447 --> 00:14:51.747
There is the upstream exploratory,
creative asset generation, things that
00:14:51.747 --> 00:14:55.517
would inform a source of truth, but
aren't necessarily the source of truth.
00:14:55.527 --> 00:14:59.567
They're more the for and exploration.
00:14:59.927 --> 00:15:03.277
And then there is this other
end of the process, which is
00:15:03.677 --> 00:15:05.127
implementation, execution.
00:15:05.137 --> 00:15:08.127
Like how do we get this
into people's real hands?
00:15:08.567 --> 00:15:12.407
And yeah, Figma are pushing
both directions simultaneously.
00:15:13.227 --> 00:15:17.177
But that second one, I think the
first one there, they are well-suited
00:15:17.287 --> 00:15:20.877
to, but I think that's a smaller
piece of the overall design puzzle.
00:15:21.767 --> 00:15:26.007
that handoff question, I think, is really
the really juicy, interesting one, and
00:15:26.007 --> 00:15:29.707
I think they're coming at it from this
sort of canvas first into code versus
00:15:30.271 --> 00:15:30.651
Jonny: Yeah
00:15:30.677 --> 00:15:33.127
Tom: other tools that are
code first into the canvas.
00:15:33.677 --> 00:15:37.867
I feel like some version of a
canvas will need to exist, but
00:15:38.757 --> 00:15:41.807
I think the sort of ownership of that
is less clear than it historically was.
00:15:42.717 --> 00:15:47.767
for me, I think there's also these extra
aspects of as we enter this era of,
00:15:49.527 --> 00:15:56.767
codifying strong design judgment into
design system or whatever the code base
00:15:56.767 --> 00:16:03.017
is for the source of truth, I think that's
moving away from just and UI elements
00:16:03.297 --> 00:16:08.227
into how do we make judgment decisions
about what our bar for quality is.
00:16:08.923 --> 00:16:09.183
Jonny: å¯
00:16:09.217 --> 00:16:10.377
Tom: more about design.md
00:16:10.977 --> 00:16:19.387
or other of, and defining our
bar for what craft is that into
00:16:19.607 --> 00:16:22.937
the way we ship products or the
way we make design decisions.
00:16:23.247 --> 00:16:27.017
And so curious what form that's gonna
take because it doesn't feel like it
00:16:27.017 --> 00:16:32.447
naturally lives on a canvas in the same
way that, sort of level design has.
00:16:32.737 --> 00:16:37.417
But there is some amount of
workflow logic in what is our bar,
00:16:37.427 --> 00:16:38.957
how do we hold everyone to it?
00:16:38.967 --> 00:16:40.027
And not just for designers.
00:16:40.067 --> 00:16:44.807
Maybe designers are the people who
are best placed to help and set that
00:16:44.807 --> 00:16:49.387
bar, but could imagine that being
used by engineers or PMs who
are
00:16:49.577 --> 00:16:54.517
making changes to the design of the
experience they're responsible for
00:16:54.517 --> 00:16:56.777
without directly with the designer.
00:16:57.577 --> 00:17:03.527
But, there needs to be some sort of
opinionated position on where is our bar
00:17:03.527 --> 00:17:08.447
for quality and our bar for craft, and
how do we, scale that more broadly across
00:17:08.447 --> 00:17:12.197
the organization without being, without
individual designers being a bottleneck.
00:17:12.397 --> 00:17:15.807
Unless those individual designers
are-- are really important features for
00:17:15.807 --> 00:17:19.417
an individual designer to be pushing
against and really handcrafting.
00:17:19.527 --> 00:17:19.997
That's a different
00:17:20.031 --> 00:17:20.421
Jonny: Yeah.
00:17:20.677 --> 00:17:24.937
Tom: But for at an organization level,
that probably isn't gonna be true
00:17:24.937 --> 00:17:26.397
100% of the time, always forever.
00:17:27.359 --> 00:17:27.679
Jonny: Yeah
00:17:27.857 --> 00:17:32.577
Tom: anyway, that's perspective
and, some of that is what you've
00:17:32.577 --> 00:17:34.537
already said, but just it, back.
00:17:34.687 --> 00:17:38.217
But I think it does mean, if we're
thinking about our design tools
00:17:38.217 --> 00:17:42.547
as, is this about execution and
implementation, or is this about ideation?
00:17:42.547 --> 00:17:47.987
I think that really what the purpose
of that tool is and how we, use it.
00:17:48.377 --> 00:17:51.077
And I think for anyone who's brand new to
design, perhaps who's listening to this
00:17:51.107 --> 00:17:56.017
podcast for the first time or as a PM
listening to this, I think throughout my
00:17:56.017 --> 00:18:02.987
career I have found that not always super
obvious that there are these two versions
00:18:02.997 --> 00:18:08.357
of design, and think AI has collapsed
those now, where you can prompt an AI
00:18:08.387 --> 00:18:11.217
tool like a Lovable or a Claude.design
00:18:12.107 --> 00:18:16.997
into creating UI that looks
convincingly polished.
00:18:17.847 --> 00:18:20.327
there's a separate conversation
about whether that's good or not.
00:18:20.707 --> 00:18:27.307
But I think it does, think further
exacerbate the challenge of having these
00:18:27.307 --> 00:18:35.427
two very different forms of design output
converging into, to make a, an assumption
00:18:35.757 --> 00:18:41.857
of how good or bad this design is I'm five
minutes into the design process versus
00:18:42.425 --> 00:18:42.655
Jonny: Right
00:18:43.717 --> 00:18:47.857
Tom: which I think, I think is an
interesting challenge to overcome.
00:18:47.857 --> 00:18:53.017
And design history, there's been
of the artifact determines the kind
00:18:53.017 --> 00:18:55.787
of feedback you're gonna get on
it and how to shape and evolve it.
00:18:56.467 --> 00:18:59.327
don't need to go down that path right
now, but I think it is this sort of
00:18:59.577 --> 00:19:05.937
interesting, the illusion of getting
to a
final artifact then having to
00:19:05.937 --> 00:19:09.441
un- back out of it to like really
interrogate those decisions and work
00:19:09.441 --> 00:19:13.917
forward is this interesting, feels
like a shortcut, but actually is
00:19:14.399 --> 00:19:14.769
Jonny: Yeah
00:19:15.197 --> 00:19:18.777
Tom: a much longer process that just
seems to start from this weird opposition.
00:19:19.077 --> 00:19:21.417
Which is fine if you're using
it for ideation and testing
00:19:21.417 --> 00:19:22.967
prototypes and ideas really quickly.
00:19:23.307 --> 00:19:26.397
But if you're trying to get something
into production sooner, it's a
00:19:28.397 --> 00:19:30.087
different way to, to think about that.
00:19:30.337 --> 00:19:31.337
Anyway, those are my thoughts.
00:19:32.823 --> 00:19:32.843
Jonny: M-
00:19:33.077 --> 00:19:33.737
Tom: else you wanna mention?
00:19:34.173 --> 00:19:37.543
Jonny: yeah, I think what I suppose
there's a bit of a call back to
00:19:38.533 --> 00:19:44.013
a conversation we had a couple of
episodes ago about sovereign AI also,
00:19:44.113 --> 00:19:51.683
which is, Figma is a US-based company
that you can imagine a world in
00:19:51.683 --> 00:19:58.393
which there's some sort of hostile or
otherwise takeover by, a trillionaire,
00:19:59.053 --> 00:20:01.103
unnamed trillionaire or someone.
00:20:02.493 --> 00:20:08.213
and then sure, the design
process is maybe less, of a state
00:20:08.243 --> 00:20:11.733
issue than access to models.
00:20:12.333 --> 00:20:17.123
But you st- just having choice,
into how you do things and
00:20:17.123 --> 00:20:18.653
having a solid alternative.
00:20:19.523 --> 00:20:24.963
I think Affinity going free and really
shaking up Adobe was just fascinating.
00:20:25.333 --> 00:20:31.393
And, Canva, Australian
founders and, less US beholden.
00:20:32.623 --> 00:20:38.473
and that's, very much in the design
world as well, just seeing, different
00:20:38.483 --> 00:20:42.403
models, different places you can go for
your design work and things like that.
00:20:42.403 --> 00:20:43.253
It's just exciting.
00:20:43.253 --> 00:20:45.533
So let's move on from config.
00:20:45.813 --> 00:20:47.123
we've done enough Figma bashing.
00:20:49.183 --> 00:20:53.623
and, it's not bashing, it's, a
healthy critique, I would say.
00:20:55.133 --> 00:20:56.073
Tom: Can I actually add one more thing?
00:20:56.073 --> 00:20:59.153
I don't know if I was clear when I was
talking about this, but the source of
00:20:59.153 --> 00:21:03.513
truth aspect of this, and I've spoken with
a few startups recently who talk about
00:21:03.513 --> 00:21:05.273
using AI to prototype really quickly.
00:21:06.013 --> 00:21:10.493
then once they have some clarity on the
direction they're going in and got some
00:21:10.493 --> 00:21:15.963
feedback from customers, then they will,
design it up in Figma from that prototype.
00:21:16.203 --> 00:21:18.083
And so Figma has remained
that source of truth.
00:21:18.093 --> 00:21:23.493
So I think
the source of truth question
will be ultimately the, decider of these
00:21:23.493 --> 00:21:27.933
big enterprises that have invested lots
of time and money and workflows into
00:21:27.953 --> 00:21:29.553
making S- Figma the source of truth.
00:21:30.143 --> 00:21:30.483
Jonny: Yeah
00:21:31.253 --> 00:21:34.983
Tom: big thing to change into code, and
if it does change into code, I think it's
00:21:34.983 --> 00:21:36.463
gonna be really cha- hard to change back.
00:21:36.463 --> 00:21:42.823
So for me, that feels like the biggest,
factor in, what's gonna, influence where
00:21:42.843 --> 00:21:44.423
the, where that source of truth lives.
00:21:44.903 --> 00:21:45.033
And
00:21:45.087 --> 00:21:48.357
Jonny: There's definitely a
design equivalent to, unscrew
00:21:48.357 --> 00:21:54.387
up my V- vibe coded app, which
is, unscrew up my sloppy design.
00:21:55.067 --> 00:21:57.087
And there is, yeah, for
a while Figma haveâ¦
00:21:57.547 --> 00:22:01.837
You've been able to import, a snapshot
of HTML in, and it converts it to Figma
00:22:01.837 --> 00:22:04.987
layers, and then you can fool around
with it and, make it look better.
00:22:07.087 --> 00:22:09.267
as you say, how long does that last?
00:22:09.677 --> 00:22:11.447
that could be Figma or it
could be somewhere else.
00:22:11.457 --> 00:22:14.717
It could be an open s- like Pencil or
some open source tool that just builds
00:22:14.717 --> 00:22:17.367
a good enough canvas that actually
makes sense to do it there, and it stays
00:22:17.367 --> 00:22:20.547
in HTML, so it's more you're actually
changing the code rather than changing
00:22:20.547 --> 00:22:22.417
a, an object that looks like the code.
00:22:24.127 --> 00:22:25.407
yeah, r- really interesting.
00:22:26.077 --> 00:22:29.567
I think these canvases and
the rectangles plays a role.
00:22:29.817 --> 00:22:30.487
it really does.
00:22:30.597 --> 00:22:33.417
it doesn't go away, and I think
you've been saying that as well.
00:22:33.977 --> 00:22:38.427
it's just whether it is an ancillary
tool versus whether it is at the
00:22:38.427 --> 00:22:42.697
center of the workflow, and I think
that is the more subtle change.
00:22:42.977 --> 00:22:47.617
Nothing dies overnight, but that is the
more subtle change that may come about.
00:22:48.137 --> 00:22:48.867
let's move on.
00:22:51.317 --> 00:22:55.077
Tom: So Jo- uh, Jo- Jonny, you
wrote, I'm gonna interrupt you
00:22:55.077 --> 00:22:57.147
there, but let's move on obviously.
00:22:57.577 --> 00:23:03.467
you wrote some thoughts down, about
jagged frontier and, how craft sits
00:23:03.467 --> 00:23:08.517
within that and some, lessons and
takeaways, reflections, over our
00:23:08.517 --> 00:23:09.967
work in the space over the last year.
00:23:11.057 --> 00:23:13.597
would love to hear any thoughts
you wanna share on that, maybe for
00:23:13.759 --> 00:23:14.389
Jonny: Yeah, I f-
00:23:14.797 --> 00:23:15.337
Tom: read your piece.
00:23:16.319 --> 00:23:20.519
Jonny: Yeah, I finally broke
ground on our Near Future.Works
00:23:20.519 --> 00:23:20.949
blog.
00:23:21.379 --> 00:23:26.099
So far the blog or the, update
section was just the podcast, and
00:23:26.099 --> 00:23:30.719
so now there is an actual written
article on the, blog as well.
00:23:31.469 --> 00:23:34.909
so I mainly wanted to do that, but I
also wanted to encapsulate something
00:23:34.909 --> 00:23:38.229
that we've been thinking about a
lot as we've been putting together
00:23:38.729 --> 00:23:44.209
creds decks and positioning ourselves
against, various other o-outfits that
00:23:44.219 --> 00:23:46.469
do outwardly similar things to us.
00:23:48.189 --> 00:23:52.009
and I think one thing that we've
really learned over the last year is
00:23:52.549 --> 00:23:59.239
that good transformation of a process,
whether it's a whole organization or
00:23:59.239 --> 00:24:05.249
whether it's within one team, from
non-AI driven to AI driven, is not
00:24:05.299 --> 00:24:06.669
as easy as you think it's gonna be.
00:24:06.669 --> 00:24:09.579
It's not a case of someone sitting
in the corner and like bashing out
00:24:09.589 --> 00:24:12.499
a new way of doing it, and then
everyone's "Cool, that works."
00:24:13.709 --> 00:24:16.279
it takes-- It's just change management.
00:24:16.289 --> 00:24:18.899
And anyone-- At my last
company was an HR tech.
00:24:18.939 --> 00:24:23.699
I saw how complex it was to change process
from the inside, and we ended up having
00:24:23.699 --> 00:24:28.789
to spend a lot of time with customers
in three-month rollout plans, g-doing
00:24:28.919 --> 00:24:32.749
tours of thousands of employees to make
sure everyone understood what this tool
00:24:32.749 --> 00:24:34.439
did, even the simplest version of it.
00:24:34.809 --> 00:24:37.949
So change is always hard when
you think about a lot of people
00:24:37.949 --> 00:24:38.989
changing at the same time.
00:24:40.579 --> 00:24:45.319
and so I wanted to try and get it
into three points, 'cause three
00:24:45.329 --> 00:24:48.309
is the magic number, and that's,
that's what trips off the tongue.
00:24:48.589 --> 00:24:52.929
So three things to really think about
when you're like, "I want to change
00:24:52.929 --> 00:24:56.059
my organization to be AI first, and I
want this transition to be successful
00:24:56.069 --> 00:25:02.019
and not just something that we're tick
boxing for the board or some other reason
00:25:02.029 --> 00:25:04.379
that isn't the best reason to do it.
00:25:04.609 --> 00:25:08.069
I want in a year's time for us
to be industry leading in our
00:25:08.069 --> 00:25:11.999
category, and I think AI is the
way that, that, we can do it.
00:25:12.319 --> 00:25:16.089
And, but I want it to go well, and I
don't want it to break our culture, and
00:25:16.089 --> 00:25:18.739
I don't want people to leave because
I'm pushing AI down their throats.
00:25:19.329 --> 00:25:22.769
and I want it to result in actually
materially good outcomes that
00:25:22.809 -->
00:25:26.299
I can point at and I can graph
rather than like good vibes and
00:25:26.299 --> 00:25:27.709
everyone spending loads of tokens."
00:25:30.879 --> 00:25:32.069
I tried to capture that.
00:25:32.179 --> 00:25:34.659
I captured it quite quickly, and I
think that this is a first version.
00:25:35.039 --> 00:25:38.829
I'm sure we will iterate over this,
and I think it captures both of our
00:25:38.829 --> 00:25:41.839
thoughts, but I wrote it, and we haven't
had a lot of chance to talk about it.
00:25:41.839 --> 00:25:46.109
But, so the three things are, a
coherent strategy I've written, which
00:25:46.109 --> 00:25:49.149
is basically like we get together and
decide why we're doing this, which
00:25:49.149 --> 00:25:51.309
is what I've j-just been describing.
00:25:52.279 --> 00:25:53.549
what is the impact we wanna have?
00:25:53.939 --> 00:25:57.079
Why, how much money do
we wanna spend on it?
00:25:57.159 --> 00:25:58.989
How much do we wanna break
the culture to do it?
00:25:59.089 --> 00:26:00.959
AKA how fast do we wanna move?
00:26:01.559 --> 00:26:03.359
all of those things should
be made centrally and then
00:26:04.549 --> 00:26:06.139
comms-ed out in the right way.
00:26:06.309 --> 00:26:09.389
Maybe this is a little bit more
like CEO stuff rather than,
00:26:10.619 --> 00:26:12.049
in the weeds for a designer.
00:26:13.209 --> 00:26:16.029
and then the second one is hearts and
minds, what we, call hearts and minds,
00:26:16.029 --> 00:26:20.997
which is- Is really just, it can't just be
one person vibe coding and pushing it out.
00:26:21.017 --> 00:26:26.507
It has to be buy-in from everyone from
like IT and procurement who need to buy
00:26:26.737 --> 00:26:32.317
a tool or give you access to a model, and
decide where the data lives and all of
00:26:32.317 --> 00:26:34.667
that kind of boring but important stuff.
00:26:34.917 --> 00:26:38.907
it needs to be the people that are
deciding the work you're doing so
00:26:38.907 --> 00:26:40.777
that they can say, "Don't worry,
do a little bit less of that
00:26:40.777 --> 00:26:42.437
work so you can spend time here."
00:26:42.547 --> 00:26:47.087
So just like getting buy-in and
support from your boss and the exec.
00:26:48.177 --> 00:26:51.597
and then everyone who's actually gonna
work on it, really just making sure that
00:26:51.627 --> 00:26:55.257
they understand and are excited about the
outcome that they're trying to get to.
00:26:56.107 --> 00:26:58.557
and it is a team sport.
00:26:58.607 --> 00:26:59.497
This is a team sport.
00:26:59.527 --> 00:27:01.817
You can't exact change on your own.
00:27:02.597 --> 00:27:03.257
That's the second one.
00:27:03.367 --> 00:27:05.107
The third one is the one that I think is
00:27:07.247 --> 00:27:13.127
where we have the strongest opinions,
and I also think where people miss out.
00:27:13.207 --> 00:27:16.307
Like the first two, fairly
obvious, have a strategy and then
00:27:16.307 --> 00:27:17.527
make sure everyone's bought in.
00:27:17.957 --> 00:27:18.327
duh.
00:27:18.627 --> 00:27:26.157
But the third one, is Not assuming
that the things you build are
00:27:26.157 --> 00:27:30.937
just automatically gonna be better
just because it's AI, and AI is
00:27:30.937 --> 00:27:33.647
magic, and it seems to happen very
fast, and you built a cool demo.
00:27:35.497 --> 00:27:40.317
I think where we've seen issues
happen is everyone's very
00:27:40.317 --> 00:27:41.687
excited by the first version.
00:27:41.897 --> 00:27:44.817
You show the stakeholders, they're like,
"Wow, c- can I have this yesterday?
00:27:44.817 --> 00:27:45.827
Let's just turn it on."
00:27:46.457 --> 00:27:49.147
And everyone gets excited about
it, and it-- what a win to get
00:27:49.157 --> 00:27:50.527
something done so quickly as well.
00:27:50.997 --> 00:27:53.527
you've done this in 24 hours,"
all of that kind of stuff.
00:27:54.517 --> 00:27:58.517
and you get so swept up in it that you
d- forget to check whether the output is
00:27:58.517 --> 00:28:00.947
any good, and this comes back to craft.
00:28:03.807 --> 00:28:07.767
the craft is ultimately still
the human's responsibility.
00:28:07.847 --> 00:28:10.307
I can't blame my tools
if something goes wrong.
00:28:11.027 --> 00:28:16.957
And so even though it's been way more
efficient than if a human did it, if it's
00:28:16.977 --> 00:28:21.877
even 5% worse, then that is a bad outcome.
00:28:22.077 --> 00:28:22.657
It needs toâ¦
00:28:22.877 --> 00:28:26.447
The, bar cannot drop, and especially
if s- what you're turning on does 10
00:28:26.457 --> 00:28:30.717
times the amount of work a- as a human,
things go wrong 10 times faster, and
00:28:30.717 --> 00:28:35.317
that sort of, descent into slop, if you
like, starts to happen really quickly.
00:28:35.317 --> 00:28:38.557
So that was what I was trying to
capture in the blog post, which I
00:28:38.557 --> 00:28:40.087
will put in the show notes for sure.
00:28:41.577 --> 00:28:46.167
but I think it's just, a vote for
craft and a vote for slowing down
00:28:46.167 --> 00:28:47.377
a little bit at the right time.
00:28:47.697 --> 00:28:52.777
People talk about this barbell
strategy around, AI generally, which
00:28:52.777 --> 00:28:55.427
is where you decide what you need up
front, and you spend more time there.
00:28:55.437 --> 00:28:57.457
And I think that's basically what
you were just talking about, Tom,
00:28:57.457 --> 00:29:01.257
is like you, you take the time to,
to decide what, good looks like.
00:29:01.557 --> 00:29:05.287
Maybe it's an art direction or maybe
it's just, a company direction, and
00:29:05.287 --> 00:29:06.387
then you spend more time at the end.
00:29:06.387 --> 00:29:09.787
And the middle is the we- the bulk of
the execution that happens quite quickly.
00:29:10.277 --> 00:29:14.957
But then at the end, it's like more
QA, more time spent looking at it,
00:29:15.057 --> 00:29:16.667
evals, all of that kind of stuff.
00:29:18.637 --> 00:29:23.377
it's very tempting to just
turn
on 50 agents and, fire your team
00:29:23.377 --> 00:29:27.927
or whatever, the, a certain group
of leaders would want to do.
00:29:28.847 --> 00:29:34.247
and w- I think we've seen the negative
side of that, and so I wanted to write
00:29:34.247 --> 00:29:37.827
that as just as a p- as a piece to be
able to share with maybe potential clients
00:29:38.447 --> 00:29:42.497
and just to establish our opinion against
the rest of the world a little bit.
00:29:43.117 --> 00:29:47.977
That said, I do think we're now at the
phase in the AI adoption cycle where
00:29:47.977 --> 00:29:51.737
a lot of people are starting to think,
actually what we built doesn't work very
00:29:51.737 --> 00:29:56.727
well," or, "It wasn't the, the silver
bullet that we hoped it would be."
00:29:57.027 --> 00:30:00.607
So I don't think it would be difficult to
persuade people that this is important.
00:30:01.307 --> 00:30:03.837
But as designers, I think
it's where we can really help.
00:30:04.437 --> 00:30:05.597
So that was,
00:30:05.987 --> 00:30:06.237
Tom: Yeah
00:30:07.647 --> 00:30:07.977
Jonny: that wasâ¦
00:30:07.987 --> 00:30:11.337
It was very quickly written though,
it's probably got typos and all sorts.
00:30:11.407 --> 00:30:13.667
I wrote it all by hand,
didn't use AI at all, so
00:30:15.597 --> 00:30:16.017
Tom: Nice.
00:30:18.057 --> 00:30:22.867
yeah, I think that-- it's, yeah, it's--
an interesting element to what you're
00:30:22.867 --> 00:30:28.397
describing of the output of the work,
and the sort of human versus AI aspect
00:30:28.397 --> 00:30:32.997
of that, but also the, process that
you go through to get to that output.
00:30:33.467 --> 00:30:41.787
And I do think something we believe is in
the importance of craft being central to
00:30:41.787 --> 00:30:47.977
how AI integrates into ways of working,
because I think there is-- there are ways
00:30:47.977 --> 00:30:55.607
that craft not necessarily be associated
with the final details and polish of that
00:30:55.607 --> 00:31:06.647
final output, but, is a mindset and a
way of iterating, refining, honing what
00:31:07.377 --> 00:31:11.677
your internal ways of working are to
get to a consistently reliable output.
00:31:12.047 --> 00:31:17.347
And so I think there's sort of-- want
to get craft just associated withâ¦
00:31:17.347 --> 00:31:22.017
And I think in the current conversation
about AI quality, I think craft
00:31:22.017 --> 00:31:25.987
has been heavily anchored in that
final, what, customers see, what
00:31:25.987 --> 00:31:27.187
that-- those final details are.
00:31:27.337 --> 00:31:28.667
And I think that's part of it.
00:31:29.027 --> 00:31:33.347
But I think there is something deeper
there as well about you can't just
00:31:33.347 --> 00:31:39.707
have people focusing only on the final
output and expect it to be high craft,
00:31:41.077 --> 00:31:47.707
the, output is there without having,
incorporating craft into the practice of
00:31:47.717 --> 00:31:49.987
building products for your organization.
00:31:52.217 --> 00:31:55.937
yeah, think the barbell is also
interesting with the sort of setting
00:31:55.937 --> 00:31:58.867
direction at the start and then
coming in and, evaluating quality,
00:31:58.867 --> 00:32:02.577
which I think are obviously the, most
high-- the highest leverage human
00:32:02.597 --> 00:32:04.527
aspects of the process right now.
00:32:05.527 --> 00:32:10.107
But I think there is a potentially a
risk of giving away too much of the
00:32:10.167 --> 00:32:18.067
middle that the craft at both ends of
the spectrum atrophies a little bit
00:32:18.107 --> 00:32:21.787
because less of a connection between
what are the materials we're actually
00:32:21.787 --> 00:32:26.457
working with and how do we get the most
out of them in this specific format?
00:32:26.527 --> 00:32:31.417
So yeah, that's maybe a separate,
slightly separate piece to your, article.
00:32:31.417 --> 00:32:32.797
But, yeah, the
00:32:32.873 --> 00:32:33.293
Jonny: No, it's
00:32:33.977 --> 00:32:35.227
Tom: you're working with is interesting.
00:32:35.807 --> 00:32:37.297
Jonny: Yeah, it's r- really interesting.
00:32:37.427 --> 00:32:41.917
And I think your point around the atrophy,
I think it's probably fairly pernicious
00:32:41.967 --> 00:32:50.077
and s- slow to spot at first, and hard
in any given moment to justify the cost
00:32:50.077 --> 00:32:51.857
of doing it when AI could just do this.
00:32:52.077 --> 00:32:54.357
AI could just do this really
quickly, so why am I doing it?
00:32:55.857 --> 00:33:01.177
and I think, said I wrote this by hand,
but writing is thinking for me, and I
00:33:01.187 --> 00:33:06.197
find it really hard to let-- to give
AI any part of writing really beyond
00:33:06.467 --> 00:33:08.187
a copy edit or does this make sense?
00:33:08.187 --> 00:33:09.027
Does it fit together?
00:33:09.597 --> 00:33:10.957
Are the, paragraphs in the right order?
00:33:11.377 --> 00:33:14.827
that's the sort of level that I'm
comfortable with AI writing for me.
00:33:16.737 --> 00:33:18.827
writing, there's craft in
writing, of course, as well.
00:33:19.017 --> 00:33:20.487
And I, would never claim
to be a great writer.
00:33:20.487 --> 00:33:23.087
In fact, I would probably say
I write worse than the AI could
00:33:23.087 --> 00:33:27.387
write what I've written, but it's
mine, so I want it for myself.
00:33:28.137 --> 00:33:34.417
And I think what with when, when people
overuse this stuff is there's too much
00:33:34.417 --> 00:33:38.462
of it for, a start, but there's also
a just sort of genericism about it.
00:33:38.462 --> 00:33:42.157
And you can see it when you ask Claude
to write an article for you with--
00:33:42.347 --> 00:33:43.667
around these three bullet points.
00:33:43.677 --> 00:33:45.437
It's a- anyone could have written that.
00:33:45.487 --> 00:33:49.697
There's no opinion there, and
it's the same with design.
00:33:49.697 --> 00:33:52.737
It's, good and convincing until
you realize that it looks
the same
00:33:52.737 --> 00:33:55.997
as everyone else's, and it doesn't
say really anything about you.
00:33:56.747 --> 00:34:01.047
so making it worse is, a weird thing to
advocate for, but craft can sometimes
00:34:01.047 --> 00:34:05.167
feel like worse but different and
getting worse and then coming back in
00:34:05.167 --> 00:34:10.017
a different way that's more powerful
or more unique or says more about you.
00:34:10.577 --> 00:34:13.137
I think it's, that's the
work really, isn't it?
00:34:13.147 --> 00:34:16.457
That's the-- There's no
shortcutting that, so
00:34:17.283 --> 00:34:17.833
Tom: Yeah.
00:34:18.043 --> 00:34:18.423
Yeah.
00:34:18.553 --> 00:34:22.663
And I think there's a, subtle distinction
there between is the thing you care about
00:34:22.683 --> 00:34:28.603
the one-off output or is the thing you
care about building the muscle of getting
00:34:28.613 --> 00:34:31.953
better at that for the 10th version
of that thing that you're producing?
00:34:32.233 --> 00:34:36.653
And in your case with writing, yes, AI
might be able to help you get a more
00:34:36.653 --> 00:34:43.513
coherent V1, but if the thing you really
care about is strengthening your reasoning
00:34:43.603 --> 00:34:49.243
of that idea or the thinking in that
space, then by article 10, your opinions
00:34:49.243 --> 00:34:53.563
are gonna be so much stronger from having
gone through the manual labor of thinking
00:34:53.563 --> 00:34:55.213
through it and writing things out.
00:34:56.183 --> 00:34:59.033
yeah, it's a, balancing act, and
I guess that varies also by the
00:34:59.033 --> 00:35:01.353
individual and what their strengths
are and where they want to focus.
00:35:01.363 --> 00:35:05.953
And then the- there's a whole category
of things that are completely valid to
00:35:05.953 --> 00:35:08.183
outsource to AI or get AI to support with.
00:35:08.193 --> 00:35:12.263
But I think being really clear on
where, how you want to use it and
00:35:12.283 --> 00:35:15.083
where it fits into your world, and I
think a craft mindset is a good one
00:35:15.083 --> 00:35:20.903
to channel that energy to the right
place, I think can, really help you
00:35:20.903 --> 00:35:22.823
get the most out of the value there.
00:35:23.487 --> 00:35:23.777
Jonny: Yeah.
00:35:23.987 --> 00:35:26.087
This is t-- I feel like this has
turned into like the broadest
00:35:26.097 --> 00:35:28.927
possible conversation about AI
and design, but that's okay.
00:35:29.107 --> 00:35:35.107
M-maybe they all just, it's, there's
an inevitability to it that, it's
00:35:35.107 --> 00:35:38.237
such a big conversation to have, and
it really is all the, conversation,
00:35:38.267 --> 00:35:39.767
and it's what this podcast is about.
00:35:39.767 --> 00:35:44.327
So we're always gonna end
up, descending into broadness
00:35:45.219 --> 00:35:45.679
Tom: Yeah.
00:35:45.719 --> 00:35:46.059
Yeah.
00:35:46.109 --> 00:35:47.729
We shou- we should, definitely move on.
00:35:47.739 --> 00:35:50.299
But I think the last thing I
want to say on this is, we've
00:35:50.299 --> 00:35:51.489
used the word design a lot.
00:35:52.159 --> 00:35:57.599
we have consciously tried to use the
word design a little bit less in the sort
00:35:57.599 --> 00:36:01.309
of broader work we've been doing, and
instead focusing more on the idea of craft
00:36:01.339 --> 00:36:07.659
because, in many organizations, design
is closely connected with the idea of
00:36:07.659 --> 00:36:11.759
craft and making sure the quality of the
work that ships is to a high standard.
00:36:12.379 --> 00:36:15.429
But I think there's definitely--
You mentioned writing craft.
00:36:15.599 --> 00:36:18.509
There's the sort of craft
of people management.
00:36:18.519 --> 00:36:22.789
There's the craft of, being a great
PM or a great user researcher.
00:36:22.799 --> 00:36:26.189
And so if you're listening to this,
don't-- Sometimes we'll say design,
00:36:26.189 --> 00:36:32.449
but we're generally focusing on that
sort of craft outcome, through any
00:36:32.489 --> 00:36:37.499
discipline that touches a product
which reaches a customer at some point.
00:36:37.983 --> 00:36:38.213
Jonny: Yeah.
00:36:38.219 --> 00:36:39.299
Tom: Anyway, that's my
final thought on there.
00:36:40.019 --> 00:36:42.529
let's switch gears and
lighten the mood a bit.
00:36:42.559 --> 00:36:46.709
I wanted to talk about, this last
weekend, I went on a camping trip, with
00:36:46.719 --> 00:36:51.959
some friends, the weekend where it was
unbearably hot, but fortunately, wasn't
00:36:51.959 --> 00:36:53.809
actually as, as hot on the campsite.
00:36:55.119 --> 00:37:03.999
but there, there's, this talk of craft
and AI got me thinking about, ownership,
00:37:03.999 --> 00:37:05.859
in this era, and is that even relevant?
00:37:05.939 --> 00:37:06.579
What does it mean?
00:37:07.249 --> 00:37:12.509
but my friend went on this camping
trip, and he a- an MP3 player, the only
00:37:12.509 --> 00:37:15.039
MP3 player that Argos in the UK sells.
00:37:15.049 --> 00:37:16.049
It was 20 pounds.
00:37:16.109 --> 00:37:24.449
And he, Sam, I loved him for his
dedication to, owning music and owning
00:37:24.469 --> 00:37:28.639
MP3s, but just hearing his stories of how
hard it was to get MP3s onto this iPod.
00:37:28.759 --> 00:37:29.809
Well, not-- It wasn't an iPod.
00:37:29.859 --> 00:37:30.799
It was a MP3 player.
00:37:31.423 --> 00:37:31.853
Jonny: Yeah
00:37:32.089 --> 00:37:36.239
Tom: the experience was made me--
took me out of my bubble a bit and
00:37:36.239 --> 00:37:41.549
made me realize how, imagining a world
without Spotify or Apple Music or
00:37:41.549 --> 00:37:47.169
these streaming music services is just
increasingly difficult to imagine.
00:37:47.807 --> 00:37:48.087
Jonny: Yeah
00:37:48.699 --> 00:37:53.049
Tom: ownership is, a sort
of strange concept in this
00:37:53.079 --> 00:37:54.759
current moment, current era.
00:37:54.979 --> 00:37:58.409
But it was also really inspiring to
see my friend wrestle
with this MP3
00:37:58.409 --> 00:38:02.669
player to try and make a playlist
and make it, and he had to bring his
00:38:02.669 --> 00:38:04.849
laptop and sync it with the MP3 player.
00:38:06.179 --> 00:38:11.299
and, Anyway, it was a, funny thing
to think about music ownership right
00:38:11.299 --> 00:38:16.159
now and the idea of an MP3 being old
school technology at this point, even
00:38:16.287 --> 00:38:16.637
Jonny: Yeah
00:38:17.939 --> 00:38:21.269
Tom: it's, probably still the standard
of how music would be shared if
00:38:21.269 --> 00:38:22.629
it wasn't for streaming services.
00:38:22.855 --> 00:38:23.235
Jonny: Right
00:38:23.489 --> 00:38:24.869
Tom: services are so ubiquitous now.
00:38:25.839 --> 00:38:26.109
so
00:38:26.175 --> 00:38:26.325
Jonny: So
00:38:26.529 --> 00:38:26.749
Tom: yeah.
00:38:26.815 --> 00:38:28.955
Jonny: he paying 99p for a song on iTunes?
00:38:29.095 --> 00:38:30.835
what's the, practically
00:38:32.013 --> 00:38:35.703
Tom: I don't know that whether he's using
iTunes or not, but he did specifically say
00:38:35.703 --> 00:38:39.183
he was buying music, supporting artists.
00:38:39.983 --> 00:38:41.123
he's a musician himself,
00:38:41.571 --> 00:38:41.801
Jonny: Right
00:38:42.723 --> 00:38:46.393
Tom: lots of, respect for
artists and buying their, MP3s,
00:38:46.643 --> 00:38:49.163
but just it's hard, hard going.
00:38:49.943 --> 00:38:54.093
another friend of mine, hosted a,
record party on Friday, which I couldn't
00:38:54.103 --> 00:38:55.163
go 'cause I was at the camping trip.
00:38:55.213 --> 00:38:58.393
But, sort of concept of this party
was to bring your own record and
00:38:58.393 --> 00:39:01.373
tell-- so everyone at the party
could play their record and tell
00:39:01.373 --> 00:39:02.603
the story of what it meant to them.
00:39:03.463 --> 00:39:05.533
which I, love that as a concept.
00:39:06.019 --> 00:39:06.319
Jonny: Love it.
00:39:07.923 --> 00:39:08.323
Tom: extremely
00:39:08.529 --> 00:39:09.039
Jonny: class millennial?
00:39:10.113 --> 00:39:10.573
Tom: yeah.
00:39:10.813 --> 00:39:11.013
Yeah.
00:39:13.673 --> 00:39:14.093
yeah.
00:39:14.543 --> 00:39:17.633
I, imagine that was a, core demographic.
00:39:18.703 --> 00:39:24.453
but, but the, yeah, the sort
of the, narrative around, music
00:39:24.453 --> 00:39:28.083
ownership and the sort of stories
associated with that, I think is
00:39:28.435 --> 00:39:28.985
Jonny: I love it.
00:39:29.353 --> 00:39:29.843
Tom: very, interesting to
00:39:29.985 --> 00:39:31.305
Jonny: I just struggle to choose one.
00:39:31.425 --> 00:39:32.675
That I wouldn't know.
00:39:33.505 --> 00:39:34.325
How do you choose one?
00:39:34.615 --> 00:39:35.185
Impossible
00:39:36.245 --> 00:39:36.635
Tom: yeah.
00:39:37.405 --> 00:39:38.455
do you own many records, Jonny?
00:39:39.545 --> 00:39:39.715
Do you know
00:39:40.333 --> 00:39:44.443
Jonny: yeah, about three or four
yards as, I think record people say.
00:39:45.433 --> 00:39:50.823
so not a big collection, but I, try
and I pick things that, it's like a
00:39:50.833 --> 00:39:53.653
subset of what I listen to, but it's
things that I feel like I would like
00:39:53.653 --> 00:39:55.113
to put on and sit and listen to.
00:39:55.703 --> 00:39:57.453
And I buy it if it's a good album.
00:39:57.503 --> 00:40:00.033
I'll buy it if it's a good
shape of a sort of album.
00:40:00.743 --> 00:40:03.713
If I think that the album tells a
story, 'cause when you put a-- as you'll
00:40:03.713 --> 00:40:08.453
know, when you put a record on, you
have to actively listen to it because
00:40:08.763 --> 00:40:12.523
you have to flip it halfway and the
number of times I put a record on and
00:40:12.523 --> 00:40:16.833
then an hour, come back an hour later
and it's just like ch, on the end bit.
00:40:16.883 --> 00:40:18.353
And I'm like, "Oh, I
forgot I put that on."
00:40:20.153 --> 00:40:24.023
but yeah, I'm a part-time collector.
00:40:25.093 --> 00:40:25.493
how about you?
00:40:26.275 --> 00:40:26.865
Tom: Amazing.
00:40:27.525 --> 00:40:33.315
I own one yard of records,
physical records, so not,
00:40:33.315 --> 00:40:34.455
the same four yards as you.
00:40:35.055 --> 00:40:37.915
think it'd probably be an easier choice
for me to decide what record to bring.
00:40:38.385 --> 00:40:45.075
But, but yeah, there is something
very, rich and interesting about the
00:40:45.075 --> 00:40:47.175
sort of physicality the, material.
00:40:47.545 --> 00:40:51.785
the idea that you're holding the
music that you can then play.
00:40:53.595 --> 00:40:54.785
anyway, we don't need to go on a
00:40:54.879 --> 00:40:55.129
Jonny: Yeah.
00:40:55.345 --> 00:40:58.815
Tom: on this, but, I think as, we get
deeper into the themes of craft and AI,
00:40:58.815 --> 00:41:04.965
we haven't yet talked about impact to
musical artists or other sort of art
00:41:04.975 --> 00:41:08.445
forms in general, and I-I'm curious if
that will come up naturally in time.
00:41:08.445 --> 00:41:14.665
But this is a small sort of glimpse
of one small aspect of, this corner
00:41:14.665 --> 00:41:18.235
of the creation of art and what
that could look like in these forms.
00:41:18.687 --> 00:41:18.957
Jonny: Yeah
00:41:19.335 --> 00:41:21.385
Tom: anyway, that's way deeper
than I was expecting that to go.
00:41:22.835 --> 00:41:25.305
final, quick, thought I wanna
share before we jump into some
00:41:25.315 --> 00:41:27.685
news is, watching the World Cup.
00:41:27.785 --> 00:41:28.615
It's been super fun.
00:41:30.095 --> 00:41:32.905
used this, Code, Claude CoWork.
00:41:33.905 --> 00:41:37.945
This isn't really a calendar hack, it's
just one prompt, but I asked Claude Code--
00:41:38.415 --> 00:41:45.885
again, I asked Claude CoWork to, add all
of the games to my calendar, obviously
00:41:45.885 --> 00:41:51.655
in the correct time zone, and then write
in the TV station that is streaming them.
00:41:52.115 --> 00:41:55.615
And it has been incredibly useful as
a way of just looking at my
calendar
00:41:55.615 --> 00:41:58.965
and seeing, oh, this game is being
streamed on this channel at this time.
00:41:59.145 --> 00:42:02.965
I also, had it add the flags to the
teams, so I could just quickly scan my
00:42:02.965 --> 00:42:04.355
calendar and see what games have beenâ¦
00:42:04.585 --> 00:42:06.835
I haven't been watching many of
them actually because of the time
00:42:06.835 --> 00:42:09.455
zone difference, and most of them
are in the middle of the night.
00:42:09.735 --> 00:42:13.865
But, it's been a very,
surprisingly useful single prompt.
00:42:14.575 --> 00:42:15.855
Have you used any, any
00:42:16.169 --> 00:42:16.359
Jonny: No,
00:42:16.425 --> 00:42:17.065
Tom: the World Cup?
00:42:17.529 --> 00:42:20.679
Jonny: that is so clever
and I've not done anything.
00:42:20.709 --> 00:42:22.879
I feel like a dinosaur.
00:42:23.209 --> 00:42:26.449
I go to bed and then in the
morning I wake up and I watch
00:42:26.449 --> 00:42:28.089
the eight-minute BBC highlights.
00:42:28.529 --> 00:42:33.869
And then when England are on,
I Google to see what channel I
00:42:33.869 --> 00:42:35.569
should turn on and that's about it.
00:42:35.569 --> 00:42:39.249
That's, I'm, I am as basic
as they come probably.
00:42:40.419 --> 00:42:42.239
wow, you- you've, brought AI to work.
00:42:42.289 --> 00:42:46.139
This morning, I was like, "I need a
haircut," and I just genuinely got
00:42:46.139 --> 00:42:49.109
annoyed that I couldn't ask Claude
to give it -- give me a haircut.
00:42:49.259 --> 00:42:51.249
So I'm, I don't know.
00:42:51.249 --> 00:42:51.469
I'veâ¦
00:42:52.719 --> 00:42:54.779
Have a strange relationship
maybe with Claude at the moment.
00:42:55.289 --> 00:42:57.519
let's move on to some news.
00:42:57.579 --> 00:42:59.239
I've got a couple of
things that I just spotted.
00:42:59.249 --> 00:43:04.089
One interesting and one silly,
or not silly, but cool and just
00:43:04.089 --> 00:43:05.529
like a beautiful piece of work.
00:43:06.099 --> 00:43:10.349
so Fable, Anthropic
announced that Fable's back.
00:43:10.349 --> 00:43:13.329
Fable's coming back tomorrow.
00:43:13.499 --> 00:43:15.849
Sonnet 5 is out today, I think,
so it'll be interesting to
00:43:15.849 --> 00:43:17.439
see the reception that gets.
00:43:17.449 --> 00:43:24.079
So these state-of-the-art frontier
models are, still advancing and
00:43:24.079 --> 00:43:25.579
it's good to see Fable coming back.
00:43:25.939 --> 00:43:30.069
There was a sort of vague, obscure
post about good conversations
00:43:30.089 --> 00:43:33.309
with government and a few more
guards being put in place around,
00:43:34.369 --> 00:43:35.469
cybersecurity and things like that.
00:43:36.619 --> 00:43:41.849
I don't think it undoes any of the damage
that was done when Fable was taken away.
00:43:42.209 --> 00:43:47.759
I think all of the alarm bells rung
around sovereign AI and not-- and being
00:43:47.759 --> 00:43:49.919
beholden to the US are still ringing.
00:43:50.089 --> 00:43:55.639
I think there's a lot of work going on
in the background, especially with non-US
00:43:55.649 --> 00:43:59.799
domiciled companies and people to try and
work out how to mitigate for the risk.
00:44:00.189 --> 00:44:02.999
One of which I think is really
interesting and seems to have blown
00:44:02.999 --> 00:44:05.599
up over the last week, which is, Z.ai,
00:44:05.609 --> 00:44:11.639
which is a, Hong Kong, Sh-
or maybe Shanghai based, lab.
00:44:12.839 --> 00:44:15.872
They, built this model GLM and GLM 5.2,
00:44:15.872 --> 00:44:19.599
which is an open weights model, is
out and everyone's raving about it and
00:44:19.599 --> 00:44:24.399
how good it is at coding and some of
the things that, people have so far
00:44:24.399 --> 00:44:26.709
relied on, these frontier models to do.
00:44:27.279 --> 00:44:32.089
And so there is like a healthy narrative
now, which is like, "Oh, maybe this,
00:44:32.309 --> 00:44:35.079
maybe the open source models can keep
up and maybe they can even close the
00:44:35.079 --> 00:44:36.429
gap on this, on the state of the art.
00:44:36.449 --> 00:44:39.509
And maybe a lot of the work we
need to do doesn't need to be
00:44:39.509 --> 00:44:40.599
done by a state-of-the-art model."
00:44:40.599 --> 00:44:47.749
So we can use, the, Fables to do the
really hard stuff and then these open
00:44:47.749 --> 00:44:51.539
source models where we can host them
anywhere and at a 60th of the cost,
00:44:51.959 --> 00:44:56.569
the token cost can do the, grunt
work around writing, writing code.
00:44:57.289 --> 00:44:59.359
so interesting.
00:44:59.359 --> 00:45:04.629
I won't go any more into it right now,
but definitely tracking it and I think
00:45:04.629 --> 00:45:11.631
that there is-- it's good news for
The rest of the world, the Fables back
00:45:11.681 --> 00:45:13.771
and the, open source models are good.
00:45:14.181 --> 00:45:19.301
It's still a Chinese model, I think
Europe and the middle powers need
00:45:19.301 --> 00:45:25.001
to work out how to have their own
frontier or near frontier, models.
00:45:25.001 --> 00:45:26.911
But it's good in the meantime.
00:45:27.161 --> 00:45:30.141
The other one that I found, and I
will share my screen for this 'cause
00:45:30.141 --> 00:45:32.921
I think it's cool and I think people
need to see it, and hopefully I'll
00:45:32.921 --> 00:45:36.441
remember to actually switch to the
view which shows the video this
00:45:36.441 --> 00:45:37.961
time, which I didn't do last week.
00:45:39.711 --> 00:45:43.421
but let me just share my
screen for Short- Shortcuts.
00:45:43.881 --> 00:45:46.591
It's shortcuts, but spelt with no vowels.
00:45:47.851 --> 00:45:49.981
so here you will see it.
00:45:50.881 --> 00:45:53.261
It's, I think, just an example of a tool.
00:45:53.531 --> 00:45:56.121
It's built by a design studio,
bra- branding studio, actually.
00:45:57.441 --> 00:46:00.291
and it-- all it does, if you're
listening, is it's got a list down the
00:46:00.291 --> 00:46:05.371
side of
all of the different, design
tools basically, and coding tools.
00:46:05.701 --> 00:46:09.601
And you can click one, and then it goes
into-- it drills down into it, and you
00:46:09.611 --> 00:46:11.291
hover over the different shortcuts.
00:46:11.301 --> 00:46:14.771
So for example, I'm in Figma, and
I've got pen tool, which is P, and
00:46:14.771 --> 00:46:18.471
you hover over it, and then this
beautiful keyboard just like animates.
00:46:18.651 --> 00:46:23.221
If I just refresh this, it like
animates in, and then you can
00:46:23.221 --> 00:46:27.091
click Photoshop and scroll up and
down, and it highlights the keys.
00:46:27.631 --> 00:46:28.591
Really simple.
00:46:29.671 --> 00:46:33.951
this is just one of those examples of the
kind of tool that you can just build now.
00:46:34.851 --> 00:46:38.711
obviously this took taste, and it
took time, and it was work for sure.
00:46:39.201 --> 00:46:43.301
But, this may have been someone who
previously wouldn't have been able to have
00:46:43.511 --> 00:46:45.401
bro- brought any of this stuff to life.
00:46:45.631 --> 00:46:48.741
Feels genuinely useful, but it's
also just like a nice piece of art.
00:46:49.361 --> 00:46:54.631
so put-- I'll put that in the show notes
as well in, beautiful design-y things
00:46:54.631 --> 00:46:57.191
that now exist that didn't previously.
00:46:57.621 --> 00:47:03.121
And this is quite a good
transition into, our workshop.
00:47:04.181 --> 00:47:04.621
So
00:47:04.643 --> 00:47:05.193
Tom: Yes.
00:47:05.913 --> 00:47:07.563
I tell, the listeners about our
00:47:07.839 --> 00:47:09.209
Jonny: Yeah, let's, yeah, you do it, Tom
00:47:10.353 --> 00:47:13.003
Tom: So I think we
hinted at this last week.
00:47:13.353 --> 00:47:22.253
We are launching our first open workshop,
and by open that means it's open to any
00:47:22.263 --> 00:47:28.693
individual who would like to join us to
build a design tool together, and we're
00:47:28.693 --> 00:47:32.233
gonna do this online on August 13th.
00:47:32.233 --> 00:47:33.463
It's gonna be a half-day session.
00:47:34.353 --> 00:47:38.273
more information, this at a
URL, which is probably going
00:47:38.273 --> 00:47:40.973
to be nearfuture.works/build.
00:47:42.273 --> 00:47:44.983
if it's not, we'll add it in the show
notes or we'll edit this out probably.
00:47:45.333 --> 00:47:46.493
But hopefully that's the URL.
00:47:47.293 --> 00:47:51.583
and just before we start recording
today for the podcast, we, tried to
00:47:51.583 --> 00:47:56.243
record a 30-second clip explaining
what the workshop was about, is about.
00:47:57.443 --> 00:48:00.813
and so we thought we'd share some
behind the scenes thoughts on that.
00:48:00.893 --> 00:48:03.673
Although aware we're coming up on time,
so we should probably keep this brief.
00:48:03.983 --> 00:48:10.853
But it was super fun to, a, short
script try and sound compelling.
00:48:11.043 --> 00:48:15.043
Although I think in a lot of ways
it sounds like an infomercial.
00:48:15.333 --> 00:48:18.193
So if you listen to it, please
listen to it, check it out.
00:48:19.113 --> 00:48:24.203
and bear with the, awkwardness of us
sounding like an infomercial and, stay
00:48:24.233 --> 00:48:29.153
for the part where Jonny lists out all
of the design tools we've recently seen.
00:48:29.203 --> 00:48:30.413
Not all of them, some of them.
00:48:31.453 --> 00:48:34.363
because, impressive that you
managed to get through that
00:48:34.363 --> 00:48:35.623
whole list without breaking.
00:48:36.495 --> 00:48:39.155
Jonny: I thought I was gonna be able to do
it in one breath, but it took two breaths.
00:48:39.155 --> 00:48:40.285
I was a bit disappointed about that.
00:48:40.935 --> 00:48:44.845
But yeah, we're, we're-- we need auto
cues 'cause reading from a script is
00:48:44.855 --> 00:48:47.715
surprisingly hard, I think, when you're
also trying to look compelling and
00:48:47.715 --> 00:48:48.845
look like you're looking at the camera.
00:48:49.395 --> 00:48:49.695
Yeah.
00:48:49.835 --> 00:48:52.325
It ended up as two minutes as--
we were aiming for 30 seconds.
00:48:52.325 --> 00:48:53.145
It ended up as two minutes.
00:48:53.145 --> 00:48:56.035
But I think two minutes is pretty
good, so I don't think we should beat
00:48:56.035 --> 00:48:57.395
ourselves up too much about that.
00:48:57.985 --> 00:49:03.875
But yes, the, the-- do check it out and
also do check out the actual, workshop
00:49:04.085 --> 00:49:06.205
because we'll be building design tools.
00:49:06.525 --> 00:49:11.465
maybe design tools like
shortcuts, maybe tools that do
00:49:11.465 --> 00:49:12.445
all sorts of different things.
00:49:12.715 --> 00:49:13.885
And we've run this before.
00:49:13.915 --> 00:49:15.105
It's really fun.
00:49:15.435 --> 00:49:17.405
Genuinely f- like fun and fast-moving.
00:49:17.405 --> 00:49:19.215
It's not watching us talk all the time.
00:49:19.785 --> 00:49:23.645
we get hands-on really quickly,
and everyone will walk away with
00:49:23.645 --> 00:49:25.505
something that they've built and
something they can take back to
00:49:25.505 --> 00:49:26.365
their team and things like that.
00:49:27.395 --> 00:49:29.535
yeah, that's on the thirteenth of August.
00:49:30.285 --> 00:49:34.305
and it's gonna be online, and
it's gonna be half a day, and,
00:49:34.615 --> 00:49:37.065
tickets will, be live soon.
00:49:37.895 --> 00:49:39.665
I think that's it really, Tom, isn't it?
00:49:40.947 --> 00:49:43.337
Tom: Yeah, I think that is, it?
00:49:43.547 --> 00:49:46.987
Hopefully we'll be live tomorrow with
both the podcast and that website, so
00:49:47.071 --> 00:49:47.401
Jonny: Yeah
00:49:47.447 --> 00:49:48.337
Tom: you can sign up for.
00:49:48.807 --> 00:49:52.357
And, this is especially suited, you
can bring others in your team along
00:49:52.397 --> 00:49:54.527
with you, or you can just come solo.
00:49:55.457 --> 00:49:59.977
we have found a lot of companies we've
spoken to have small design teams.
00:50:00.847 --> 00:50:07.177
there's, two or three designers there,
and people are curious to dig into this,
00:50:07.217 --> 00:50:12.737
but it's hard to justify doing a whole
team session when the team is small.
00:50:13.527 --> 00:50:16.967
so if you're a solo person out there
or you're in a small team, or even
00:50:16.967 --> 00:50:21.067
if you're in a big team but your
company is not, doing as much as you
00:50:21.067 --> 00:50:25.517
would like to do in exploring this AI
space, then this really is for you.
00:50:25.657 --> 00:50:28.417
So you'll check it out
and at least consider it.
00:50:29.637 --> 00:50:33.747
and if not, then, if you do check it out
and decide not to do it, then we'd love
00:50:33.747 --> 00:50:35.617
to any feedback or thoughts you have.
00:50:36.187 --> 00:50:38.687
Both, for that, but also
for the podcast in general.
00:50:39.017 --> 00:50:41.037
we have been getting some
good feedback so far.
00:50:41.317 --> 00:50:46.037
It's been really helpful in us shaping,
our format, the stuff we're talking
00:50:46.037 --> 00:50:49.837
about, and, and potential future
guests that we're gonna be inviting on.
00:50:49.837 --> 00:50:53.077
So please, if you have any ideas,
if you listen to this, have some
00:50:53.077 --> 00:50:55.277
thoughts you wanna share, us.
00:50:55.297 --> 00:50:58.317
We have a, an email address,
in fact, that Jonny set up.
00:50:58.357 --> 00:51:00.977
I think it is podcast@nearfuture.works.
00:51:01.107 --> 00:51:01.307
So
00:51:01.343 --> 00:51:01.603
Jonny: Yep
00:51:01.607 --> 00:51:03.847
Tom: a note there or ping
either of us individually.
00:51:03.887 --> 00:51:04.667
We'd love to hear it.
00:51:05.375 --> 00:51:07.395
Jonny: You can-- It's okay to
just tell me to brush my hair and
00:51:07.395 --> 00:51:08.895
stop wriggling around so much.
00:51:09.045 --> 00:51:10.665
That's acceptable feedback.
00:51:13.585 --> 00:51:14.115
Tom: Excellent
00:51:15.455 --> 00:51:16.085
Jonny: Let's call it.
00:51:17.515 --> 00:51:18.645
one, one in the can.
00:51:19.095 --> 00:51:21.665
Thanks everyone for listening,
and, see you next week
00:51:23.027 --> 00:51:23.247
Tom: Thank you