Speaker 1: Pushkin. I'm Jacob Goldstein and this is What's Your Problem,
Speaker 1: the show where entrepreneurs and engineers talk about how they're
Speaker 1: going to change the world once they solve a few problems.
Speaker 1: My guest today is Anna Katrina d Letski. She's a
Speaker 1: mechanical engineer who started her career at Apple, where she
Speaker 1: worked on the Apple Watch that was responsible for we
Speaker 1: call it packing the suitcase. So the industrial design team
Speaker 1: makes beautiful surfaces of like what it's going to look
Speaker 1: like on the outside, and the product design engineers figure
Speaker 1: out how to get all the parts inside that suitcase.
Speaker 1: If you will, you got to get all the parts in,
Speaker 1: and then you know that product needs to be robust.
Speaker 1: When Anna was working on the watch, she saw a
Speaker 1: massive problem, not just with the watch or even just
Speaker 1: with Apple, but with all of electronics manufacturing. The problem
Speaker 1: is this electronics manufacturing is incredibly inefficient, incredibly wasteful. And
Speaker 1: I'm not talking about consumers throwing devices away. I'm talking
Speaker 1: about the manufacturing process itself, what happens before the product
Speaker 1: even leaves the factory. So Anna left Apple and started
Speaker 1: a company called Instrumental to try to solve that problem
Speaker 1: in our conversation. Anna laid out the problem really clearly
Speaker 1: when she explained what happens when a new device is
Speaker 1: about to go into production. It starts with a sort
Speaker 1: of practice build, when a few hundred or a few
Speaker 1: thousand devices are assembled as a test. If you're part
Speaker 1: of a team of engineers working in your cushy office
Speaker 1: in Kupertino, this is the moment when you and your
Speaker 1: team have to go and actually see this thing you've
Speaker 1: designed being built. You'd all get on a flight and
Speaker 1: you'd fly in earlatest China. It's where a lot of
Speaker 1: stuff is built, although today maybe it's somewhere else in
Speaker 1: Greater Asia. And then you land in a city, and
Speaker 1: then you'd get into a factory van and you might
Speaker 1: drive for an hour and a half or two hours
Speaker 1: out into a very rural part of China, and that's
Speaker 1: where you'd have a massive manufacturing center. And then we
Speaker 1: would be there for about ten or fourteen days. What
Speaker 1: is the point of you being there. I'm there trying
Speaker 1: to find issues, find problems, find parts that aren't fitting,
Speaker 1: find quality issues with parts. So like we expect there
Speaker 1: to be problems and quality issues with the parts, Anna said,
Speaker 1: she's not allowed to talk about specific preproduction problems they
Speaker 1: had with the Apple Watch, but she did give me
Speaker 1: a hypothetical source of problems the antenna. So, okay, picture
Speaker 1: of factory with hundreds of workers packing all these tiny
Speaker 1: little parts into the watch. One of those parts is
Speaker 1: the antenna, this tiny little thing the sizes of like
Speaker 1: a one inch piece of dried spaghetti, and it has
Speaker 1: to go in there just right so that the watch
Speaker 1: can talk to the world. If the antenna isn't just right,
Speaker 1: the watch doesn't work. Yeah, So let's say hypothetically, you
Speaker 1: at the end of the line, you have a pile
Speaker 1: of units that the antennas don't work. The antenna's really challenging.
Speaker 1: It's like near a lot of metal and antenna's a
Speaker 1: metal don't don't mix, and so the antennas don't work.
Speaker 1: What you have as an engineer is test station results
Speaker 1: that say this signal is low. It could be an
Speaker 1: eighty percent tissue, like eighty eight out of ten don't work.
Speaker 1: It could be a you know, point one percent issue.
Speaker 1: You only have one that doesn't work. It made a
Speaker 1: thousand and nine hundred and ninety nine of them work,
Speaker 1: But what's wrong with this one? Because if you make
Speaker 1: a million, what's wrong with that one? If you make
Speaker 1: a million, one in a thousand is a big problem, right, yes,
Speaker 1: exactly exactly, And so in development you care about every failure. So, okay,
Speaker 1: so you have this problem the antenna doesn't work whatever
Speaker 1: often or once in a while, what do you do?
Speaker 1: We would gather up those physical units, which is non
Speaker 1: trivial to get all those units in one place in
Speaker 1: this big factory, and then we would very carefully start
Speaker 1: to rip them apart to try to get more data
Speaker 1: about what's wrong with these units? Why don't they work? Now.
Speaker 1: One of the things that's interesting about antenna specifically and Watch,
Speaker 1: if you've ever seen a teardown of the watch, is
Speaker 1: when you're taking it apart, you could very easily be
Speaker 1: destroying the evidence of the thing you're trying to find. Oh,
Speaker 1: like you just budge the antenna a tiny little millimeter
Speaker 1: or whatever, and that matter, yes, and it matters. And
Speaker 1: so you might try to take some X ray images
Speaker 1: before you disassemble, so you have some idea literally there
Speaker 1: you have an X ray camera, yes, which is like
Speaker 1: a three dimensional X ray, And then you take them apart,
Speaker 1: and you'd very carefully try to figure out what was
Speaker 1: going wrong. And sometimes those things are obvious. You open
Speaker 1: it up, it has no antenna in it, So that's
Speaker 1: why the antenna doesn't where. Sometimes it's very obvious. Sometimes
Speaker 1: it's not obvious, and like, as a skilled engineer, you're
Speaker 1: looking at it, You're like, I have no idea, And
Speaker 1: then you start looking at the process. You go, you walk,
Speaker 1: you know, fifty meters up the line to look at
Speaker 1: where they're putting the antenna's in, and you're watching that
Speaker 1: process and trying to see is there something happening here?
Speaker 1: Are there like are there screwdrivers swinging across the line
Speaker 1: that are like going to hit the parts and knock
Speaker 1: the antenna? I mean, I feel like there's sort of
Speaker 1: two layers of problems here. Right. There's the fundamental problem of, oh,
Speaker 1: we manufactured a million of these things and we know
Speaker 1: ten thousand of them are going to break, right. That
Speaker 1: is just a straight up problem. There is also the
Speaker 1: like engineers like you have to go fly to China,
Speaker 1: you know, stand on an assembly line and just hope
Speaker 1: they catch things, hope they figure out where the problem is.
Speaker 1: Not even they're looking for problems, they don't even know
Speaker 1: their problems are yet, Like I would go to a
Speaker 1: build and it would be a successful build if we
Speaker 1: left the build with one hundred issues in a spreadsheet
Speaker 1: of different things that we needed to fix. So that
Speaker 1: was the success. Like, the more problems you find, the better.
Speaker 1: I mean, it's a success because you found it because
Speaker 1: you know the problems are there, and you're just worried
Speaker 1: that you're not going to find. Yes, that's like your
Speaker 1: real nightmare problem if you're like a design engineer, right,
Speaker 1: the one that like you don't know is a problem
Speaker 1: until you've shipped a million pairs of earbuds or something.
Speaker 1: The technical term for that is an escape. So that's
Speaker 1: a failure that has escaped the problem escaped the factory. Yes, yes,
Speaker 1: and so escapes are what essentially then cause returns and
Speaker 1: if we go back to that waste, yeah, which is
Speaker 1: hugely costly. Right, it's bad for the reputation of the
Speaker 1: manufacturer because it's like, oh, it's a crappy product, bad reviews,
Speaker 1: not a reliable problem Amazon, bad reviews, and you've got
Speaker 1: to like refund the money, send the person a new one.
Speaker 1: So it's costly on many levels. Yes, yes, and so
Speaker 1: returns should be avoided, and you avoid returns by reducing escapes,
Speaker 1: and you reduce escapes not only by figuring out all
Speaker 1: the things that you can possibly test for. And so
Speaker 1: that's why there are testations on the line, but the
Speaker 1: testation can't test for everything. Did you just live in
Speaker 1: fear all the time of missing some terrible problem? I
Speaker 1: don't even know how to answer that. I think that
Speaker 1: a good engineer is a paranoid engineer. So for me,
Speaker 1: as an engineer, I thought it was kind of silly
Speaker 1: that there is so much luck involved. You just have
Speaker 1: to get lucky and catch the problem before it goes
Speaker 1: into production. Luck like that, yes, and so you're trying
Speaker 1: to find you're relying on luck to find things that
Speaker 1: you can improve in development. And then there's also like
Speaker 1: the scramble and the heroism that happens when you do
Speaker 1: have a problem that everybody learns about. Oh, we have
Speaker 1: this problem. So then you have this fired drill where
Speaker 1: everybody flies in tries to figure out what's going on.
Speaker 1: There's tons of freneticism and activity, and this just seemed
Speaker 1: like a waste, Like why is it that we're so
Speaker 1: reactive versus proactive? Why is it that like I don't
Speaker 1: have access to the data that I need as an
Speaker 1: engineer to actually proactively solve these problems. I have to
Speaker 1: go and like hope versus No. After the break, Annah
Speaker 1: launches Instrumental, a company that's trying to help engineers solve
Speaker 1: the problem of finding problems. Help him go from hope
Speaker 1: to know. That's the end of the ads. Now we're
Speaker 1: going back to the show, So just a reset here.
Speaker 1: Anna has landed a job at Apple, the company where
Speaker 1: engineers dream of working, this amazing technology company, and yet
Speaker 1: she decides to leave. So I asked her in the end,
Speaker 1: what made you quit your job and go start this
Speaker 1: new company, Instrumental. I can share some thing that that
Speaker 1: you can use, but it's maybe it might be a
Speaker 1: little sideways to what you're talking about, but it's the
Speaker 1: true reason I started the company. So about a year
Speaker 1: before Apple Watch shipped and the world knew that it
Speaker 1: even existed, I actually had a personal tragedy happened in
Speaker 1: my life. My husband was killed by a drunk driver.
Speaker 1: Oh my god, and I was twenty seven, he was
Speaker 1: twenty seven. And I realized that life is precious and limited,
Speaker 1: and you don't know when your last day is going
Speaker 1: to be, and so you want to be proud of
Speaker 1: the days that you have and how you spent them
Speaker 1: and the impact you could have on others, and also
Speaker 1: reevaluate the justification for my existence on this planet. And
Speaker 1: I decided that Apple is great. I'm glad I was there,
Speaker 1: but it can't be my life's work for me. I
Speaker 1: felt like I needed to do something bigger. And the
Speaker 1: big problem that we all need to solve is how
Speaker 1: we build stuff is so wasteful. That is a more
Speaker 1: meaningful direction. And there is a big problem that I
Speaker 1: know that I have some intuition about how to go solve,
Speaker 1: And so I took what I understood as like, wow,
Speaker 1: it's like really hard to find and fix these issues.
Speaker 1: We're wasting so much money, so much physical stuff. We
Speaker 1: are pumping so much chemicals into our rivers, we are
Speaker 1: burning so much energy. We are wasting human lifetimes of
Speaker 1: time doing things that don't matter. It's just wasted, and
Speaker 1: we need to figure that out. We need to change
Speaker 1: how we build, We need to change how we think
Speaker 1: about building products. So this is like a little maybe
Speaker 1: sappy for your audience, but this is the true reason
Speaker 1: that like really made the change of thinking about away
Speaker 1: from thinking about, oh, my job as an engineer, I
Speaker 1: make stuff too. Oh, my job as a human is
Speaker 1: to figure out how to do the things we need
Speaker 1: to do better. So Anna decides she's going to try
Speaker 1: to make electronics manufacturing better, more efficient, less wasteful. And
Speaker 1: to do this, she and an engineer she worked with
Speaker 1: at Apple decide to start a company. They call it Instrumental,
Speaker 1: And when it started, they had one big idea. Instead
Speaker 1: of forcing engineers like Anna to frantically run up and
Speaker 1: down the assembly line hoping they'd spotted every potential problem,
Speaker 1: they would put dozens of cameras up and down the
Speaker 1: line to capture the entire assembly process for every single device.
Speaker 1: It's the idea that there is value in this data
Speaker 1: that today does not get collected, and so the actual
Speaker 1: core pieces, Let's go get all the data. That's the
Speaker 1: that's the core innovation here. Let's go get all the data.
Speaker 1: The data in this case is visual data. What does
Speaker 1: everything look like as this phone or this watch or
Speaker 1: whatever is getting put together? Is that right? That was
Speaker 1: the first data set that we went after was the
Speaker 1: image data set, because there isn't one. So we're creating
Speaker 1: a data set that didn't exist before. And as you know,
Speaker 1: as they say, a picture is worth a thousand words.
Speaker 1: When you take a picture, you don't need to know
Speaker 1: in advance what you're going to be looking for in
Speaker 1: the picture. It's a very high resolution data set, and
Speaker 1: then you can come back with twenty twenty hindsight and
Speaker 1: look at the picture and be like, oh, like, here's
Speaker 1: a problem in that picture. And so that was the
Speaker 1: initial concept of like, we need to find where these
Speaker 1: issues are, which means we need to see them. We
Speaker 1: work in the physical world, so we need to see them.
Speaker 1: Remember I was talking about the antennas, where you had
Speaker 1: to carefully take them apart, and as you took them apart,
Speaker 1: you'd sometimes damage the evidence you're looking for. Well, if
Speaker 1: you have images of them as they went together, then
Speaker 1: you don't maybe have to take them apart, or you
Speaker 1: maybe have additional data about what they looked like as
Speaker 1: they were going together. But you don't know which ones
Speaker 1: are going to be failures in advance, so you take
Speaker 1: pictures of all of them and then you have the
Speaker 1: ones after the fact that ended up being failures. You
Speaker 1: have those images. So that was like the first idea.
Speaker 1: So the basic ideas. You take pictures of the whole thing,
Speaker 1: and you identify, you know, whatever, the serial number on
Speaker 1: each say, watch each device that's going down the line,
Speaker 1: and then if there's one device that doesn't work, you say,
Speaker 1: show me all the pictures of that one, and then
Speaker 1: you say, how is that one different than all the
Speaker 1: ones that do work in the pictures? Yes, yes, But
Speaker 1: it's not just about figuring out what's wrong once you
Speaker 1: find a problem, right is It also about getting better
Speaker 1: at finding problems in the first place. So discovery, we're
Speaker 1: able to solve the discovery problem for our customer. We
Speaker 1: built algorithms that look for anomalies, and so what's an anomaly.
Speaker 1: An anomaly is something that's different from the other ones.
Speaker 1: So if you build a population of units, they should
Speaker 1: all look the same, Okay, a bunch of devices, right,
Speaker 1: The ones that look different are probably interesting, and so
Speaker 1: we build algorithms to find the ones that look different.
Speaker 1: And that was kind of the first offering that we provided,
Speaker 1: And so our customers were able to use that combination
Speaker 1: of the photo record with the algorithms that would highlight
Speaker 1: automatically the things that were different and interesting, and they
Speaker 1: were able to use that to find issues. Basically, one
Speaker 1: of these things is not like the other, yes, exactly,
Speaker 1: So like, oh, this one's bent a little bit, this
Speaker 1: one's the parts supposed to be black and it's white.
Speaker 1: Is that a problem? Maybe not? Maybe we highlight those
Speaker 1: things and then the next piece is okay, well what's
Speaker 1: causing like problems? Okay, so you've built a system that
Speaker 1: is better at identifying for finding problems. So now even
Speaker 1: if a device pass all the tests, your system will say, well,
Speaker 1: you want to check out this one missing screws because
Speaker 1: it just looks a little different missing screws. Okay, so yeah,
Speaker 1: like that missing screws, there's no screw tester. You're right,
Speaker 1: like missing screws. Devices will actually miss screws. I'm so
Speaker 1: naive that I'm like, well, surely a device wouldn't be
Speaker 1: missing a screw, but one hundred percent, it's like one
Speaker 1: of the top ten defects in production is missing or
Speaker 1: extra parts, extra screw just to make up for the
Speaker 1: other one that's missing a screw. On average, they have
Speaker 1: the right number of screws. Yes, on average they have
Speaker 1: the right number of scares. So we need to be
Speaker 1: able to find issues. We need to be able to
Speaker 1: help engineers fix them, and then we need to help
Speaker 1: them make sure they don't come back. Those are kind
Speaker 1: of the three things that we have to do. So okay,
Speaker 1: those are the three key things Anna's company does to
Speaker 1: solve this big problem and to tile those pieces together.
Speaker 1: She gave me a case study, a case study from
Speaker 1: a company that was trying to build a webcam and
Speaker 1: the company was having trouble with the antenna. The antenna, which,
Speaker 1: as Anna told me about earlier in the interview, is
Speaker 1: this crucial part that is surprisingly hard to get right.
Speaker 1: They always fail. There are very sensitive parts, and all
Speaker 1: of our connected devices really rely on their antenna performance.
Speaker 1: So you don't think about it, but you know it's
Speaker 1: an important part. And so we had a customer who
Speaker 1: had failing antennas and they were able to take that
Speaker 1: group of that population of units and they were able
Speaker 1: to actively, like root cause it to three different things.
Speaker 1: And so this is actually the next piece of the puzzle,
Speaker 1: which is we need to find root cause. And so
Speaker 1: in this case, the customer was able to see a
Speaker 1: couple of different things. The first thing they found is
Speaker 1: a group of those failures was actually had to do
Speaker 1: with the alignment of a connector that was connecting the antenna.
Speaker 1: So the connector, if it was like shifted a little
Speaker 1: bit this way, it was good, and it was shifted
Speaker 1: a little bit the other way, it was bad. And
Speaker 1: this was very subtle. This is not something they had
Speaker 1: like a specification. This is a discovery. Okay, so the
Speaker 1: angle mattered and they didn't know that in advance. Okay,
Speaker 1: Now this is also maybe too much in the weeds.
Speaker 1: But there are a lot of reasons, and antenna can
Speaker 1: fail in a lot of different ways. So it's not
Speaker 1: just like, oh, if they're failing, they're all the same
Speaker 1: root costs. Actually, there could be a group of different
Speaker 1: causes that cause failures. So you have two different phones
Speaker 1: from the same build, both of which have the antenna
Speaker 1: that doesn't work. It might be a different reason for
Speaker 1: each phone that the antenna doesn't work, which makes it
Speaker 1: harder to solve. So you solve one problem, but then
Speaker 1: some of the phones still don't work. Is that what
Speaker 1: you're saying, Yes, yes, that's very common. They also found
Speaker 1: that the software version that they were using on the
Speaker 1: tester was also correlated to the failures, so most of
Speaker 1: the failures were from one particular tester, So in fact,
Speaker 1: it wasn't a bad antenna. It was a test for
Speaker 1: some of those units, not all of them. Some of
Speaker 1: them still had the connector coming out at a wrong angle.
Speaker 1: Yeah yeah. And then the last one on the same
Speaker 1: group of failures, in the same group of failures, there
Speaker 1: was another group of units where what the image based
Speaker 1: algorithms found as a high correlation to the color of
Speaker 1: the circuit board. And so color doesn't affect performance, but
Speaker 1: it was a different vendor. One circuit board was like
Speaker 1: a slightly different shade of a color than another, and
Speaker 1: so that means like the vendor of that circuit board
Speaker 1: was for one of the vendors that made that circuit
Speaker 1: board was more likely to have failing in it. So
Speaker 1: that gives engineers then three different things. They can go
Speaker 1: chase down. They can go chase down a process is
Speaker 1: year around the angle of the connector. They can go
Speaker 1: chase down like the drifting test station and work on
Speaker 1: calibrating the testations. And then they can go and investigate
Speaker 1: if there's something meaningfully different between these two vendors of
Speaker 1: circuit boards. So they're able to continue building, but they
Speaker 1: have now three specific things they can go do, whereas
Speaker 1: without instrumental they would kind of be guessing. So, like,
Speaker 1: what's the sort of frontier for you? What's the thing
Speaker 1: you're trying to do that you haven't quite figured out yet, Like,
Speaker 1: what's the next problem to solve? Yeah, I mean so
Speaker 1: it goes back to the reason for being for the company,
Speaker 1: the reason for being being that twenty cents of every
Speaker 1: dollar that's wasted in manufacturing, we haven't solved that problem yet.
Speaker 1: What does that require? We need to change how we
Speaker 1: think about how we build things, how we design things,
Speaker 1: the process of iterating through that development process, the process
Speaker 1: of what happens when it goes into production, what happens
Speaker 1: when you return units? And what do we do with
Speaker 1: that information from your return as a consumer. And today
Speaker 1: we're really not doing that as an industry. Not gathering
Speaker 1: data in a meaningful way is that we're not gathering data,
Speaker 1: we're not thinking proactively. As an engineer. If I'm designing something,
Speaker 1: I'm thinking about, you know, the next build and production,
Speaker 1: but I'm not I'm not necessarily thinking about, like how
Speaker 1: can I develop this product's that I can capture the
Speaker 1: most data from it the fastest, the earlier in the
Speaker 1: process versus later in the product. Like everybody knows their
Speaker 1: data is valuable and there's stuff in there that could
Speaker 1: be valuable, but they don't know how to value it
Speaker 1: because the problems haven't happened yet. When they're on fire
Speaker 1: quote unquote and they are spending a million dollars a
Speaker 1: month on returns, they know exactly what the value is
Speaker 1: in the data that they don't have, Yes, but when
Speaker 1: they haven't started the program yet and they don't know
Speaker 1: what fires they're going to have, they don't know how
Speaker 1: to value having the data. And like preventing those problems
Speaker 1: in the first place, the vision is that that data
Speaker 1: is enough and then if you figured out how to
Speaker 1: harvest that data, you can actually build lines that improve
Speaker 1: themselves and then you eliminate the waste. So this new
Speaker 1: different way of doing things, like can you just tell
Speaker 1: me sort of specifically, like a few details, what would
Speaker 1: it be like, what would it look like, what would
Speaker 1: be happening in this world? Everything gets built cheaper, everything
Speaker 1: gets built with less waste. And when that happens, we
Speaker 1: have maybe we have cheaper products, we have maybe more
Speaker 1: profitable companies, we have less waste going into the world,
Speaker 1: less physical waste, chemicals and rivers, less energy use, less
Speaker 1: human lifetimes wasted, And it's just thinking completely differently about
Speaker 1: like that manufacturing actually is a machine itself, and that
Speaker 1: we need to optimize that whole process as a machine
Speaker 1: itself versus a means to justify the ends of like
Speaker 1: we need we need to get products out the other
Speaker 1: end of the line. In a minute, the Lightning Round,
Speaker 1: Anna tells us what mechanical engineers know about the world
Speaker 1: and the inefficiencies out in the wild that grind her tears. Now,
Speaker 1: let's get back to what's your problem? Great, let's do
Speaker 1: the Lightning Round. Are you ready? What's one piece of
Speaker 1: advice you'd give to someone trying to solve a hard problem.
Speaker 1: I love that question. I love it. I had a
Speaker 1: science teacher in high school taught me how to solve
Speaker 1: hard problems because I was working on science research. I'm
Speaker 1: a science fair kid, and he taught me to break
Speaker 1: those problems down into manageable pieces. So like, if you
Speaker 1: can take smaller steps and understanding a problem and the
Speaker 1: small steps you can do, then it becomes easier to solve.
Speaker 1: So as somebody whose job is sort of to find
Speaker 1: errors and inefficiencies in the world. Is there some some
Speaker 1: domain something you encounter in your daily life that you
Speaker 1: just you really want to optimize inefficiencies in things that
Speaker 1: cause lines really irk me, like at the airport or
Speaker 1: in like a restaurant, like anything that feels like a
Speaker 1: non optimal like kind of scheduling and line that causes
Speaker 1: a line of humans. That is something that I that
Speaker 1: I noticed, and I just like really grinds my gears.
Speaker 1: Of all your patents, which one's your favorite, I'm gonna
Speaker 1: go with my first patent more because of what it means.
Speaker 1: So I share my first patent with actually who is
Speaker 1: now my co founder, Sam Weiss, and we met in
Speaker 1: two thousand and nine at Apple, and that's actually the
Speaker 1: summer that we invented our mutual. It was our mutual
Speaker 1: first pattern, and we had to build essentially a switch
Speaker 1: very similar to you know on the side of an
Speaker 1: iPhone there's like a little ringer switch that you can
Speaker 1: you can kind of down. So we had to build
Speaker 1: a switch like that that had a very small ford
Speaker 1: back there, like it needed to fit in a weird shape.
Speaker 1: And so that was our first pattern. That pattern will
Speaker 1: never see the light of day. There will never be
Speaker 1: a switch that has made in that design, but it
Speaker 1: was cool. That's awesome. What do mechanical engineers know about
Speaker 1: the world that nobody else really gets? That everything is
Speaker 1: imperfect and different from every other thing. Is there a
Speaker 1: particular piece in say my iPhone that is the one
Speaker 1: that is like has caused the most manufacturing problems, the
Speaker 1: most problems on the assembly line? Is there some piece
Speaker 1: that's like, oh, that piece is the one. I never
Speaker 1: worked on phones, so I don't know specifically, but in
Speaker 1: general in products, the antenna, anna, anything with glue, and
Speaker 1: anything having to do with water, So those are the
Speaker 1: three things. It's like. It's like the antenna's heart displays
Speaker 1: are hard too, but like, so basically everything. Is there
Speaker 1: some trick that mechanical engineers use when something isn't working,
Speaker 1: like a remote control or whatever. I always think about it,
Speaker 1: is it a hardware problem or a software problem. If
Speaker 1: it's a software problem, reboot it. If it's a hardware problem,
Speaker 1: I don't know, check the batteries. I make sure it's
Speaker 1: plugged in. Anna Katrina shad Letsky is the founder and
Speaker 1: CEO of Instrumental. I have a request for you this week,
Speaker 1: and it is this. Please let me know who you
Speaker 1: want to hear on this show. You can email me
Speaker 1: at problem at Pushkin dot fm. That's problem at Pushkin
Speaker 1: dot Fm. Or you can tweet at me at Jacob Goldstein.
Speaker 1: Today's show was edited by Robert Smith, produced by Edith Russolo,
Speaker 1: and engineered by Amanda k Wong. I'm Jacob Goldstein, and
Speaker 1: I'll be back next week with another episode of What's
Speaker 1: Your Problem