TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Technology

    Metamuse

    Tools for thought, product design, and how to have good ideas.

    Advertise
    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    https://museapp.com/podcast/transcripts/60-real-materials/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: I think designing is just the process of picking the best option that you have gone through, but you need to go through that process. The more time that that process takes and the more expensive that process is, the less you experiment and you just fall back and you default to what we know. But that’s not where great ideas often come from. 00:00:24 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac, but this podcast isn’t about Muse the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGranaghan. Hey, Adam. And today we’re joined by Dan Lacivita of Play. Hey guys. And Dan, in addition to your duties as co-CEO of a startup, I understand you also have a particular management challenge this summer. 00:00:53 - Speaker 1: Yes, I have two boys, 9 and 7. They just got out of school. So we are thinking of outdoor physical labor activities for them over the summer. The last one was actually cleaning the garage floors, my son. was squeegeeing the water out and he’s like, Dad, this is really satisfying. I was like, yeah, you know, you have to do the other side of the garage too, and then it became immediately less satisfying for him. Yeah, so, we’re coming up with a lot of ideas for those activities. 00:01:21 - Speaker 2: For some reason, I’m reminded of a beloved 80s movie on male mentorship, which is the Karate Kid, and the famous doing chores as a way to learn to be a martial artist, so maybe there’s some angle like that. 00:01:34 - Speaker 1: Yeah, life lessons through chores. I don’t know if they’ll like that, but that’s the, you need to do this in order to play video games, so that’s the model we’re going with. 00:01:43 - Speaker 2: And tell us about the journey that brought you to play. 00:01:46 - Speaker 1: Yes, so 42 years old, father of two boys, prior to play starting play with my other three co-founders, June, Michael, and Eric. We all worked together at an agency called Firstborn. It’s a design and technology agency. We’re headquartered in New York City. I actually started there in 2004 as a flash developer, for anyone who remembers the good old Flash days. And when I left, I was CEO. June was our chief creative officer, Michael was our founder, Eric was one of our lead engineers. And yeah, we were designing and building websites, mobile products, AR experiences for our clients. We actually sold the business to Dentsu about 10 years ago now and through the process of creating all of those products for our clients, especially mobile products, we’re just always thinking about the tools that we were using, and this is when Sigma was very early days as an agency, we just moved over to Sketch and, you know, my partner June was just always talking about how we’re using the same input devices, you know, for our design tools, but we’re using our phone as a creation device in many other areas and so that kind of kernel of the idea led us to leave Firstborn and then start play. 00:03:02 - Speaker 2: And I feel this is quite a unique angle. I guess there are plenty of places where you use a phone to create content, typing out a quick email or something like that, but something like a design or especially an interactive prototype, you know, we think of that as something where you really got to be at a desk, mouse, keyboard, big screen, and doing that on the phone, which is really optimized to be a consumption device. It’s unusual. How is that borne out so far in your product to date? 00:03:29 - Speaker 1: I thought it was a crazy idea initially too, when June initially talked to me about it, and I was like, how are we gonna create a design tool on a phone with that real estate. And so the interesting and probably there’s many aspects of the entrepreneurial journey that are fun, but I think the early days of just watching the team. Create different UI patterns. We landed on sort of this, I think, unique slider UI that allows you to design on the phone while not having the interface getting in the way of what you’re actually designing. So I think that was a really interesting part of the process in the early days. And I think what’s been more exciting and maybe a little unanticipated is As we started to design a design tool for the phone on the phone, we realized, oh, we have this whole sort of sandbox of things that Apple has created, all of these native controls, native gestures that we can now tap into and then layer our GUI on top of, if you will, and give designers the ability to design with the real things, right? The real materials that engineers will ultimately use to make the product that they’re designing. So, it’s been A fun journey so far, you know, it’s unlike traditional design tools that require you to context switch and stimulate the mobile experience plays really the first tool to make contextual design for mobile possible, so there’s no proxies or simulations or syncing to mirror apps. You are sort of getting your hands into the clay immediately and beginning to craft inside of the final medium that the users will ultimately experience things on. 00:05:07 - Speaker 2: And that speaks to me for sure because I’ve written about creative process as being largely about the feedback loop, the iteration loop, how quickly can you try something and see the results of the value of, for example, what you see is what you get editing and word processors, direct manipulation. I’ve written about this in developer tools where you very often have a long compile run. Cycle and the closer you can get to instantly make a change and see the results sort of the better, even though in many cases that’s not fully practical and so in some senses you’re designing it on the device and so there isn’t some switching, as you said, to some other location. It’s all kind of right there in the same context. 00:05:49 - Speaker 1: Yeah, it was one of the things that June had talked about early on, is like, you know, let’s say I’m designing something for a client to review, it’s, you know, mobile app screens or prototype for a mobile app. I have to get all those designs on my phone, like through a mirror app, right? Or just save JPEGs. This is even before mirror apps were, I mean, they’re still not really that great. It’s like, but then I want to look at that when I’m not at the office. Like, I want to look at that when I’m walking through the park, or maybe we’re designing for a certain persona and they’re going to use this app in a grocery store. Like, I should look at these designs when I’m in the grocery store and I’m in that environment, and then I’m going to see things that I want to change, but I can’t change them in that moment. I have to like write it down or take a voice memo, wait until I get back to the computer or back to the office the next day, then make those changes. And then if I want to see those changes back in that, you know, sort of environment, I have to go back to the grocery stores like, I just want to make that change right there in that moment. And then see how that feels, or maybe have a few different versions of that and then see how that feels. And so, I think for him and as we talked about it, there’s this unique magical moment when you’re looking at something in your phone, like a design that you’ve created, and then you’re like, oh, I wonder what would it look like if this was changed, and then you could just change it just directly on your phone and it’s kind of a very cool and empowering moment. 00:07:07 - Speaker 3: That’s interesting to me because as an early phone user, I was surprised by the extent to which the mobility and ubiquity of the phone was an advantage. I think that’s kind of obvious in retrospect, but for someone who grew up with a desktop computer, you know, everything was there. You had a big screen, you had a keyboard, it seemed great. Just being able to access a thing all the time turned out to be amazing in ways that I didn’t anticipate. I hadn’t thought previously to apply it to design. Again, I’m back at the square of, oh, it’s design work, you gotta be at your desktop to do it, right? But not so much. 00:07:34 - Speaker 2: You mentioned needing to come up with new kinds of interactions because the phone doesn’t have a big command vocabulary or established precedent for, well, I think sort of creation activities in general, but certainly design work in the specific and in my brief experiments with the app like one that certainly catches your eye right away, maybe this is what you were referencing is you kind of see the prototype filling most of the screen, but you swipe to the right, which sort of spatially speaking drags in the left hand. Side of layer list which will look very familiar to a sketch Photoshop type person and indeed those are often on the left, but here they’re just sort of off screen they’re sort of in the spatial metaphor of the mobile world they’re sort of hovering off to the side until you slide them in and then there’s another one on the right that you sort of pull in that actually. It gives you adding horizontal and vertical stacks, buttons, all that sort of thing, and then there’s sort of a properties panel that slides up from below that lets you edit stuff. So that certainly speaks to us where, you know, working on the iPad trying to make a thinking tool we do end up having to like invent a lot of stuff from whole cloth, which is a pretty big hassle or a lot of work or takes a lot of time relative to working in the more known space, but it’s basically a lot more fun as a designer and engineer and product builder because you do have this open frontier that Now that all possibilities are open. 00:08:53 - Speaker 1: Yeah, I agree. I think it’s certainly fun in the creation process. And then when you design those small magical moments, it’s fun for the user too. And I think even tools that exist for creating something or have a purpose behind what I’m doing can also still have those moments of fun or you know, sort of interesting interactions that smile, right? That say, wow, that was actually a cool thing that I experienced and so. When we were designing the slider, Eric, you know, our lead engineer and my partner was like, oh, well, maybe we can just drag the slider vertically as well. So like I’m actually moving the knob on the slider horizontally, but if it’s in the way of something on the screen, I could just move that entire slider up and down. And it was just those little moments and as they compound, then the UI starts to come together and actually becomes something far more functional and usable and interesting to use for the user as well, I think. 00:09:51 - Speaker 2: So our topic today is designing with real materials, and longtime listeners of Meta Muse will know this is something we’ve we’ve touched on with past guests. Andy from Not Boring Software has a great post called Honor the Material where he talks about basically furniture and how you can design using whatever the particular material is, whether it’s wood or molded plastic or steel that you can use. That in a way that fits the material and then in the digital realm we’ve spoken with David from Webflow who talks about how Dreamweaver and other kind of past visual website builders maybe one reason they didn’t kind of quite ever seem to click is because they don’t respect the underlying materials of the web, that’s HTML, CSS, the box model, URLs, pages, links, etc. So, Dan, what does designing with real materials mean to you? 00:10:44 - Speaker 1: So, designing with real materials is something that I think early on for us, we realized was possible because we have access to, as I mentioned before, this sandbox that Apple has created. So even the most basic example of a button. I’m gonna design a button in FigMA or sketch, and the buttons are gonna have different properties, right, color properties, there’s probably text in there, maybe there’s an icon, probably has some padding, maybe a corner radius that has all these different properties. And even when an engineer looks at that button in a FIMA file or a sketch file or XD file, there’s actually a significant amount of code that needs to be written just to get that button to look exactly the same. When I’m writing it in X code, when I see it inside of a design, and that’s just a button. So then if you zoom out of that and think, well, OK, well then what do I need to do for a card or a stack of cards or an entire page or a multitude of pages that then have different states and interactions, it becomes a lot. And so, we realized that Why would I design a button and play when I could just use the native UI button, for example, that Apple creates, which is how an engineer is probably going to build the actual product. And this is the most basic example, right? So I could just add a native button to my page, and when I’m designing that button and play, I’m actually manipulating all of the properties that exist. In that UI button that an engineer is going to either include or choose to not include when they code it. So we’re doing a couple of things. One is where Giving, I think, more power to designers to, instead of writing a bunch of SWIFT UI code or UI code to, you know, create that button, we’re surfacing all those same properties, but in a way where they can design with them. And then when they communicate that, Perhaps with a developer handoff or collaboration feature, that engineer isn’t just looking at a vector-based rectangle on a page, they’re looking at the same real materials that they’re actually gonna build with. And if you further that, then you start to get into live maps or input text fields or UI collection view or, you know, how stacks are used. And so what we do is we say, well, what are all of the things that I’m gonna use to build a real application. Let’s surface those up as real materials for a designer to use when designing, instead of using replicas of those materials. 00:13:17 - Speaker 2: And I’ll argue it flows both ways. There you’re talking about the engineer has to do this effort to kind of, you know, replicate what’s in the design mockup that comes out of the more general purpose designing vector editor tool, but it actually flows back the other way too, which is you see that. There’s big libraries and components that are here’s your iOS system components, here’s your Android system components, those need to be updated every time a new version of the OS comes out where you’re essentially simulating all of those things inside the design tool and then you go back to the ultimate target. Someone needs to build that button and then they need to kind of extract from your vector drawing what parameters are going to go into that button. So it seems like that could have the ability to short circuit a lot of that back and forth. 00:14:02 - Speaker 1: Yeah, exactly. And I think our general purpose design tools do a lot of things really well, but a lot of their strength lies in that what I would call generality, right? Like I can use a tool like FigMA or Sketch to design a website or an app or a wedding invitation or a poster or a business card or anything, which is incredible. So I think in the context of designing products, they’re great for designing. A blueprint for the house, but they don’t really get us closer to designing the actual house, cause they’re not using the real materials that are gonna be used designing that end product. So, I think the closer designers can get to that point, not only does it make it better for engineers, but to your point, it educates the designer, and I think it empowers them to design with those real materials. 00:14:48 - Speaker 2: When we spoke earlier, you pointed out that the sketches and figmas of the world are general purpose vector editors, whereas what you’re buil…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/61-listener-questions-2/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: This ends up becoming a question about file standards more than it does about application functionality. I can take a notion document and fairly easily translate that into a text file, a very linear document format. There’s currently not really a file format for spatial canvas. Right now there’s just not a good way for Muse to talk to another spatial canvas app. 00:00:30 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac, but this podcast isn’t about Muse the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGrenigan. 00:00:45 - Speaker 2: Hey, Adam, and another colleague, Adam Wulf. 00:00:48 - Speaker 1: Hey everyone. 00:00:49 - Speaker 2: And Wulf, I understand you recently spent some time in prison. 00:00:53 - Speaker 1: That’s true, and it’s so good to be out with everyone again. I, of course, was not technically in prison, well, I guess I was. I volunteer with a program called the Prison Entrepreneurship Program. They actually help felons who are near release go through and kind of 3 month entrepreneurship school. They do character development and then learn about starting their own business, and really help them get their feet under their ground again, find their sea legs when they get released. So they do a lot with employment. And housing and support, and a lot of education on the inside of the walls, and a lot of support on the outside of the walls and family reunification, and it’s really just a wonderful program that helps. Inmates helps their families, and ends up helping society. And so the, the big number that matters is national recidivism, which is the number of people who get released from prison and go back into prison, is extremely high. It’s somewhere around like 40 or 50% end up going back into prison. And graduates of this program, it’s as low as like 5 or 7%, and so it just has a dramatic effect for these men and for their families. And so it’s been really fun to volunteer with the past. Gosh, probably 5 years, something like that. So, yeah, if anyone ever wants to be locked in prison with me, then give me a shout out. We’ll make it happen. 00:02:18 - Speaker 2: Sounds like a really worthy program. Well, we’ll link them in the show notes. I’m definitely a believer that how a society treats the people that need to be removed for sort of justice reasons and what you do when they’ve, you know, fulfilled their debt to society, as the saying goes, and how you make a transition back to normal life says a lot about it. It seems like a really great program you’re involved in there. So we can jump straight into our topic today, which is listener questions. This is our second mailbag episode. Mark, you and I did one year and change back, and I think it was quite a lot of fun to go through all the questions people submitted. And now feels like a good time to me just because we’re 2 months or so out from the launch of our 2.0 product and the dust is still settling, but in many ways we spent a lot of the last two months just answering questions through all channels Twitter. Hacker news, but most especially through our support channel, that’s hello@museapp.com and the in-app thing. So we’re in a question answering mood and we have a lot of common questions that we thought would be good to kind of address on air as well as we put out a call on Twitter for folks to submit questions. We’ve got lots of really interesting ones, more than we’ll have time to answer, so we’ll do our best to get to as many of them as we can. You fellows ready? Let’s do it. Yeah. So I guess we’ll start with roadmap just because that tends to be the biggest or most numerous questions are in that category, what features we building and when, but we can go from there and how people use Muse or how we use Muse, things about the broader ecosystem, tools for thought, as well as more even broader than that, some things about how our team works and even some things about Ink & Switch. So the nuts and bolts of roadmap doesn’t work for you. You can jump forward a little bit and things will get more far ranging. But yeah, starting at the beginning here, so I think a broad question many people ask, but here I’ll quote from Penny Chase who basically just said, I’d like a glimpse into the Muse roadmap, and we answered that question mark, I think a year, year and a half ago, and I think it included, you know, going local for sync and going multi-device and having desktop apps. So check, has that roadmap changed other than what we’ve accomplished since then. 00:04:30 - Speaker 3: Well, the good news is that with this launch, I think we’ve got a lot of validation on the direction that we’ve been going since day one, really, which is this idea of a tool for helping you have better ideas that spans your iPad, Mac, iPhone, eventually the web, and is very rich. And what we’ve heard from our users, I think, is, yes, and let’s see the rest of it. And just to give a few buckets there, I think one building on the local first sync, you have the phone, that’s a pretty obvious gap for us right now, a more complete phone app, both in terms of making the phone a better tool for getting things into and out of your corpus, and also being able to look up stuff on the go. You can also see something with the web, sharing on the web or even a full blown web client. and also building on sync. We talked during our tech episode how that’s really the foundation for collaboration, both synchronous and asynchronous, so I wouldn’t be surprised if we see something there. And then back in the what we call like app features, there’s some pretty standard stuff that I think we’re missing. Better search, linking, these are things that people ask for very often. Another one I would say is more rich tech support. That’s a really foundational content site, and I could see other content types like videos and better support for free ride web pages and so on. And then there’s a few more things I think we need in terms of like organizing and managing your content, stuff like non-spatial collections we’ve had on our list for a long time, a better inbox, which might be a variant of that. But those are, I think the main buckets on the horizon and then I still have on my medium to long term was this idea of end user programming or like scriptability, programmability more generally. I think that’s incredibly powerful and we have a really compelling foundation for that. I think we need a little bit more on the core app first. 00:06:11 - Speaker 2: Yeah, one way I’ve summarized it to myself and others is Muse 1 was a multimedia thinking canvas for iPad only. Muse 2 goes multi-device. We’ve got the desktop and iPad, the local first syncing between them, phone, I think is going to be part of the 2. X series, at least that’s my hope, kind of it’s part of that vision. It’s everywhere you need it, and then Muse 3 is where you get into the sharing collaboration, making it more than. It will always be first and foremost a personal tool as something that is better connected to the outside world, both other humans, but also other tools through integrations and things like that. And then yeah, maybe the end user programming feels like the, I don’t know if that’s Muse 4 or just kind of the finishing move that ties it all together. 00:06:58 - Speaker 1: In some ways I see use one as use the teenager and Muse 2 as used the college graduate, and now we have all of the education and skills and life foundation to be able to bring Muse to this great career beyond in collaboration and teams and end user programming and text formatting and we finally entered adulthood, I think, ready to go out into the workforce and make a difference in the world? 00:07:23 - Speaker 2: Absolutely. Now on some specific features folks have asked about, a big one here is Zoom, being able to zoom in closer on some things, usually images or PDFs, and being able to zoom out further, especially boards as your boards get bigger and more complex, and a representative tweet on this is from our friend Marsen Igna, who says, where can I read more about why Muse has no zoom out for bird’s eye view of my board? Yeah, it clashes with the navigation gesture, but I’d love to work at 50 to 75% zoom. 00:08:01 - Speaker 1: When I think of Zoom, I think of solving at least two different problems. The first problem is on a very large board, I want to zoom out and still be able to work and move selections around to kind of reorganize a very large desk or very large workspace. The second problem is I’m working on a very large board, and I want to quickly jump to a different location. Scrolling is currently just kind of wandering around in the wild, and I’d really like to be able to see a map and quickly go from the bottom left to the top right or the top middle. So I think whenever we do build Zoom, we need to think about it in that kind of context of which problem are we trying to solve? Do we find a solution that maybe can solve both problems? It’s not obvious to me which of those is the most important to start with, or the right lens to look at the feature through. 00:08:55 - Speaker 3: Yeah, Zoom is a very subtle challenge in Muse, just mechanically speaking, say you want to zoom out, OK, you pinch to zoom out on a board. How do we know that that’s different from wanting to zoom out to the next level up? That’s a problem we can solve, right? And you can have a quasi mode to toggle between the two, or you can have a detent in there somewhere or something. It’s just it’s quite subtle. Another challenge with Zoom that we’ve known about since our research in the lab is with these freeform canvases, especially if you have Zoom and especially if you have infiniteness, you have this real risk of becoming lost. Like you’re looking at this solid off-white thing and it looks the same regardless of where you are and how far you are zoomed in, and people just get totally discombobulated. And so we’re trying to push back against that a little bit. And this isn’t just a challenge for boards. We’ve also got a lot of requests for zooming into PDFs and images. So there’s a lot of stuff going on. You got zoom in, you got zoom out, you got navigation versus the document, you got different from document types, got temporary versus permanent. There’s a lot of stuff to figure out. So the answer is we just gotta sit down and do it. I think it’s very doable. It’s gonna take some time and some design work, and maybe some cutting of the Gordian not as Adam would say, you know, just get the 80% in there. I think we’ll get it done eventually. 00:10:05 - Speaker 2: We actually even discussed that as a potential thing to work on post launch. We were looking for things that would be more smaller projects, quick wins, crowd pleasers, just things to refresh our palettes after working so long on this big massive release with big data migration and so on. And actually the conclusion we came to is it was too big of a project because we do want to think about all that stuff holistically and even if we do just carve off a small piece of it to do first, just doing a kind of boring and obvious way to do it like there’s a zoom level drop down or something like that we think will quickly create the problems that I think make a lot of other software not that enjoyable to use, which is disorientation and so on, and it’s particularly bad in the infinite canvas setting, but yeah, we need it, we badly need it as people’s boards get more sophisticated, as people are bringing in more different types of PDFs and images as they just want to do more things. Yeah, you need the ability to zoom and we’ll solve that hopefully much sooner than later. 00:11:03 - Speaker 1: I think Zoom is also related to accessibility and potentially text size and text formatting, which we’ll talk about in a little bit. But tech sizes for some users can feel a bit small in use, and being able to zoom into a board or into an image in PDF mark, as you mentioned, is also related in some ways to allowing for custom text sizes or larger headers or text formatting, just generally being able to. See content no matter what your screen size happens to be, if you’re on a small iPad or a large iPad or a big screen. 00:11:37 - Speaker 3: Yeah, then we’re getting into the real Pandora’s box on the implementation side of when do you rasterize this content. If you only have one zoom level, you have a lot of flexibility and kind of do it whenever you want. But if you’re zooming all over the place, you either need to rasterize later or essentially suffer the effects of rescaling, so it’s quite gnarly. 00:11:55 - Speaker 2: A related one that’s challenging technically is dark mode. Again, another one we’ve gotten many, many requests for over the. Well, years now, and one of my favorite stories actually, actually one of the best ways to ask for features is to tell a story, as we would say in our podcast episode about storytelling, attaching something to a story makes it much more memorable. So one story I remember well was someone writing that they were on an international flight, you know, overnight flight, 10 hours, 12 hours or something, and they spent the whole session basically with Muse and they had a bunch of PDFs loaded up and deep reading and deep thinking, perfect opportunity for that, right? But they’re in this darkened cabin. They turn their screen brightness down, but it’s just still too bright and they’re kind of afraid of waking the other passengers and so on. 00:12:44 - Speaker 2: Oh, that’s such a vivid image just blasting the cabins, but many folks have asked for it for similar reasons or just because they like dark mode. But because we have the zooming interface that uses what we call internally snapshots, which are basically those thumbnails you see of the boards that give you this, you have this scaling transition, this sense of seamless zoom and traveling around in this kind of open world where you’re never loading a document or what have you, and that’s very nice, but the snapshot rendering. actually pretty CPU intensive. You see this also, if you log in to a new device like an iPad with an account that has a lot of data in it and it downloads it all, the downloading it may take a while, but then generating all the snapshots actually will also cause your device to be pretty busy for a while if you have a lot of boards and deeply nested boards and so on. And so dark mode has the problem that, OK, now we basically need to generate new snapshots for every single board and do we keep both of them all, you know, do we make two all the time and slow down every regeneration every time you change something for a feature that maybe most people won’t ever use. Or is it when you switch modes, do we turn on the regeneration and suddenly your iPad is heating up and you grinding the CPU for 5 minutes while it tries to re-render everything and maybe you just want to check it quickly and then you switch it back and now it’s grinding again for another 5 minutes, so totally solvable, but I guess it’s, as with many things because we have this unique zooming interface and nested boards, that’s something that sets me apart, makes it unique and pretty special to my mind. But it also can make what seem like basic features much harder. 00:14:17 - Speaker 1: I use Zoho mail for my male client and their dark mode. It was an interesting choice because they need to be able to support dark mode for attachments that anyone can send and so it’s not only their own interface, but they’re trying to create a dark mode for the content of the email itself and what they settled on was for those attachments to literally invert the colors, which was functional but a bit jarring. 00:14:51 - Speaker 2: When greens turn into purples…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/62-community/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: You want to achieve mastery in some sense in your life. So all these things come together and for some people, community becomes very addictive. I’ve certainly been in communities about products and games, where the game or product became a. And the importance because the community in itself just became my main driver to come back to this group of people nerding out about something that I wasn’t even using or playing all that much, but I love the ideas about it. 00:00:35 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac, but this podcast isn’t about Muse the product. It’s about the small team and the big ideas behind it. I’m Adam Wiggins, joined by my colleague Mark McGranaghan. Hey, Adam. And our guest today, Ramsey Out of LogSeek. 00:00:54 - Speaker 1: Hi, Adam, I’m Mark. Great to be here. Thank you for having me. 00:00:57 - Speaker 2: And I understand you started your professional life as a Spanish teacher. 00:01:02 - Speaker 1: Yeah, that’s correct. When I finished my associate degree, I was about 16 years old here in the Netherlands. You’d leave high school very early, so 16 years old, I started my associate degree and then finished when I was 18. So I enrolled in college, did a double degree in Spanish language and culture, and then also teaching it, and that is basically what, yeah, triggered. The obsession with learning and specifically learning languages, so both natural languages and computer languages. That is how it all started, all the sleepless nights trying to figure out why something is not working or why I don’t understand something. 00:01:43 - Speaker 2: Can I assume you probably fell down the space repetition on key rabbit hole at some point. 00:01:49 - Speaker 1: I’m still hooked 15 years after discovering it, so I just finished before we started this call, I just finished my 100+ Italian repetitions, which I’m now doing, so I’m learning Italian through immersion, flashcards, and a lot of TV shows, so, yeah. 00:02:07 - Speaker 2: Netflix has definitely been a very big boon to language learners, particularly with their very solid audio and subtitle selections and the ability to rewind and relisten when you didn’t quite catch something, and so on. 00:02:19 - Speaker 1: And the tools build on top of that, so there are actually tools that will let you capture subtitles with a screenshot. I think there’s even options to capture the audio, like a piece of audio with it. So, yeah, definitely the tools in the last decade have definitely made language learning easier. Obviously the flashcard tools, but also note taking tools, obviously, as you dive deeper into a language, really make it a study project. That is basically, I started with the flashcards and then I moved more and more towards the personal knowledge management nerding out over the more intricate parts of the languages that I was learning. 00:03:01 - Speaker 2: I guess I can see the path there. This is the part where I’d normally ask what was the path that brought you to lugs seek, but I think that almost answered the question a little bit, especially when you talk about the, is it the Think stack Club is your kind of online learning platform that maybe bridge the gap between those two endpoints. 00:03:18 - Speaker 1: Yeah, so in like very quickly run through my curriculum, so basically after graduating as a Spanish teacher and teaching for several thousands of hours because internships are very early in the Netherlands, I couldn’t find a job as a teacher. Teacher. So I ended up actually as a telemarketer for 2 years on the phone with IT managers, mostly decision makers or stakeholders in IT departments trying to get appointments like physical appointments for colleagues of mine. And I would just cold call people each and every day. That’s where my hunger for learning came in very handy because I had to learn a lot about the IT space so what companies operate, what technologies are there, so not just from a software perspective, like I knew obviously operating systems, but also servers, networks, complex systems, so I had to learn a lot. So note taking became more of a focus for me as I was on the phone, taking lots of notes. Finding basically little rabbit holes to go down to as someone would mention something like a technology on the phone, I would just say, oh yeah, oh yeah, sure, sure, and and the meanwhile I would write down some terms and then spend half an hour researching that, taking some notes, like we had an internal wiki as well because there were more guys like me who didn’t know anything. Too much about the IT like certain parts of the IT ecosystem, like the corporate IT ecosystem, and we’re eager to learn, so we’re just a bunch of guys eager to learn and practicing our skills and that ended up laying the groundwork for me becoming more and more technical, advancing through the corporate IT letter, basically joining Oracle, becoming a customer success manager. And that helped me listen more and more to customers, figure out what are the issues they run into, so obviously, interviewing skills, note taking again, very important, came into play, and that’s how in the end, I ended up with Lux seek as I was doing more and more online with Community just because it’s a passion of mine. I like it and I got into community when I started with language learning. And I just kept at it, learning through community as I progressed in my career. I, again, found my way back to community and then see, OK, what have I learned in all these years? What have I see. Not work like communities that I’ve been a part of that went like south that became very toxic, and what are the communities that still thrive now that I look back 15 years later, there’s some language learning communities that have become super toxic, nobody is there anymore and other communities thrive and there’s some clear markers I would say that show, OK, this will. More or less predict if a community will thrive in the future or if it continues on this path, if it’s going to basically die out at some point. 00:06:24 - Speaker 2: Yeah, I think language learning is uniquely suited or perhaps I should say tends to be something that really benefits from community. I think a lot of things do, many different interesting skills and career things and so on, but maybe language we’re learning can be just so continuously frustrating. And you just need this, of course you need the internal motivation, but there’s something about others going through it at the same time. As you, I continue to think that the community aspect, almost the like group therapy aspect of Y Combinator is actually one of the things that makes it successful in the Silicon Valley entrepreneurship world is just being around some other people who are going through the same thing as you experiencing the same struggles, and then when the going gets tough, as it always does, you can kind of find strength in the others who are going through it with you. So yeah, I could see where language learning would be just ideal for that in some sense. 00:07:16 - Speaker 1: Yeah, it’s both for learners, so there’s a lot of knowledge in the language learning community. Obviously, there’s also drama like in any other nerdy niche, there are people very contentious about flashcards versus no flashcards or grammar focused study over just watching TV shows. There’s always some reason to have discussions, but it’s not just useful for learners, but I’ve also found it useful as a teacher and I think that’s how I got into community in the first place. I as a teacher, most language teachers that I know and also myself included, we don’t really do rigorous academic research into what works and doesn’t work in class. We work off a lot of anecdotal evidence, so trying stuff out in the classroom, sharing that with colleagues within the school, but then there’s also, especially here in the Netherlands, there are many programs to connect through universities, connect teachers and have teachers share experiences. And then also connecting them online. So there’s a lot of useful work happening there, that’s also how you see innovation happening in language learning products. So, Duolingo is a very simple example of making something like space repetition. Mainstream, even though before people would never mess with Aki, it can offer a way for teachers to say to their students, hey, use these different tools to get more input. And then as learners become more fanatical, hopefully they will discover unki other methods that are more suited to their style of learning and how they like to get fluent in the language. 00:08:59 - Speaker 2: And why don’t you tell our listeners what is Loseek? 00:09:03 - Speaker 1: Yeah, so LogSeek is a tool that helps you organize knowledge and make that knowledge your own. So what does that mean? Let’s unpack it a little bit. So when you open Loxy for the first time, it looks like just another outliner tool. So just a tool that you write in bullet points and you can in dense or out dense blocks. 00:09:24 - Speaker 2: And the classic outliners here would be Emacs, or mode or workflowy maybe. 00:09:29 - Speaker 1: Yeah, so the less technical ones would be dynalyst, work flowy, on the more technical spectrum you would have Emacs, for example, that are well known example I think for many listeners would be Rome research. And then in the spirit of Rome research, Lexi is an open source outliner, but it’s built like Rome and some other tools like Obsidian, it’s built on top of a database. So even though you work with just plain text, it’s all stored in a database as well, so all your data is also stored in a database. So there’s a lot of data about the data, a lot of metadata about the individual blocks, like the outlines. And that including the data that you add yourselves, that yourself, for example, through links or tags or some other simple database structure that you create, which we call property. So if you use properties, you can basically give information about the data and that will help you. Build processes, so basically pipeline systems you can use Lexi, which is very popular for project managers who take many notes and then want to reservice those notes in a single dashboard or students who want to reservice all the notes related to a class and then easily turn them into flashcards. So here again, the flashcard thing is coming back, so many students use. Logs seek, also because it’s free, it’s very easy to write just your notes in the outline as you’re sitting in class and then add a few simple hashtags to turn something into flashcard. And that is, I think the true power of Luxeek is that obviously it’s free, which for many people is a plus. It’s open source, so it’s very hackable, but also it for many people it breeds some trust that even if we decide to stop with the company or go into a direction that our user base doesn’t like that then they can continue with the app and continue developing it themselves if they want. And then obviously, also the ease of use because it’s in the end just an outliner, I think that has attracted many people to logs seek to use it, at least as a scratch pad for stuff that’s on their mind that they don’t want to forget and that they want to have an easy way to find back their notes. 00:12:01 - Speaker 2: And it’s interesting that you sort of lead with the outliner, the indented bullet points, and then you mention links, you know, when I think of Rome, which obviously is a source of inspiration, it makes me think of almost the category I think they sort of invented, which is what I call, would usually call a knowledge graph. Now obviously there’s a history, a much deeper and longer history of linked. Databases, the web with hyperlinks is sort of the ultimate of that, but also something like a team wiki, like you mentioned using in your previous career steps, but also, obviously something like notion, how important do you think of linking as being in sort of the logseek product? 00:12:39 - Speaker 1: I think linking and indentation, so basically the Document as a mind map, so instead of having a text document or just a paper where you have a linear piece of text, you have more like in a mind map structure in computer talk, call it a tree-like structure, you know, and programming language. So That I think is the root also of the web. So those are two things that are root of the web. So if you look at a normal web page, HTML page, the documents that you look at, the code is structured in a tree-like structure, so it’s basically an outline. Every web document is basically an outline. So, that is one principle that many people are not aware of, but that I think once you rock that idea. Then you can become much more flexible with your knowledge. You don’t have to flesh out an arguments linearly. You can just choose to upload your thinking and then branch out. So just like as you would design a web document, you would first maybe start with some headings, then you start filling those headings in the same way in an outliner, you would start with the top level blocks. And then as you become more and more nuanced, you add more and more blocks underneath and then linking helps to link to any data that is not part of that same block of information, so that same tree like branch, you can then link to other branches basically. So that will allow you to hop from branch to branch. So that’s why I lead with the idea of an outline structure because Understanding a graph database, like graph databases were around before Rome existed, like far before, so it’s not a new concept, but many people are not familiar with it. Whereas if you say there’s no taking tool, it’s like a mind map, you just create a collection of mind maps and the outline is nothing more than a mind map. For many people it’s much easier to understand, even though I still use terms like tree-like structure and traversing the tree, for example, or branches. I still think you should learn that as a user, if you’re serious about knowledge work, then you should definitely become more familiar with the language. But the first principles of it being a branch, your notes being just a bunch of branches, I think that’s the most important thing. And then obviously there’s nowadays also the meme, oh, I will just use Apple notes, why do I need a complex note taking tool? I think if you think that way, probably Apple Notes is good for you, but if you want to think very thoroughly over time, if you want to refine your thinking, you need to have some tools to support that. So if you don’t have some deep intellectual projects that you’re working on, Maybe designing a product or mastering a language, for example, that in itself I would count as an intellectual endeavor that takes a long time. If you don’t have that, just use Apple notes to scribble down your grocery lists and stuff that you don’t want to forget, but don’t overcomplicate things. So I’m really focusing on the people who are not familiar with this, but who have some kind of yearning to organize their knowledge and are willing to put some time in it to learn the basic principles of a tool to help their thinking. 00:16:09 - Speaker 2: The term note taking in some sense is overloaded and even we pushed back in the muse kind of positioning, messaging basically what goes on our homepage describing what it is. I always pushed back against the note taking or didn’t love that because it does make you first think of scribbling down a grocery list in the default notes app on your phone. And I do that, and I think it is correct to call that note taking, but it’s also correct to call it note taking that you’re developing a large body of work over a long time in the process of a deep intellectual process like learning a language, writing a book, deve…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/63-platforms/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: I think every platform kind of has this tipping point where you start to see like, hey, this feature, this product is getting a lot of traction, and people building on any platform should realize they are doing R&D for the primary platform at all times. Every feature you release, every experience you have is an opportunity for the original platform to be like, hey, that’s a great idea. 00:00:29 - Speaker 2: Hello and welcome to Meta Muse. Us is a tool for deep work on iPad and Mac. But this podcast isn’t about me use the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Adam Wulf. 00:00:43 - Speaker 2: Hey, everyone. And joined today by Joe Watkin. 00:00:47 - Speaker 1: Hey folks, great to be here. 00:00:49 - Speaker 2: And Joe, you have an interesting background with creative tools including GitHub and Abstract, you’ve had your own startup doing calendar slackbots and other calendaring things, but before we talk about all that, I’m very interested in your side project ballot share. Can you tell us about that? 00:01:06 - Speaker 1: Oh yeah, yeah. Ballot share is a is a labor of love. It’s much less of a business than a fun project, and it really just centers around helping people get more information when they’re about to vote. And so, People usually want to vote for one or two things when they hit a ballot, but it’s all of the minutia stuff that people don’t really have a really good sense of what to vote for or who to vote for on really local issues, but those are the stuff that really, you know, impacts them. And so Ballot share is just a site where you can see who’s endorsed things all the way down the ballot to like your local city ballot initiatives. And you can also create your own endorsement around things that you think are important and share that with friends. So the most common use case we see is people say, oh, like I have a friend who’s really plugged into education, so maybe I could ask them who to vote for for the school board president. And so they send you their endorsement and you kind of see it in a grid where you can kind of compare all of the endorsements that you want to compare. It was built for the last election cycle and we’re hoping to revive it again for the midterms. 00:02:14 - Speaker 2: I really like that idea of a sort of using your trust network if that’s the right way to put it. Maybe we get some of this implicitly, you know, there’s people I follow usually like substack where they do political analysis and to some extent I’m sort of trusting if I’ve come to trust that their analysis is good in some cases it’s that I’m reading their analysis and better understanding the issue, but in some cases it’s that I go, OK, this person. Seems to be pro this thing and I basically trust them, so therefore, I’m gonna kind of outsource that decision a little bit, especially for, as you said, all these finer details and local things that maybe you can’t deeply research each and every item. So it feels like it’s naturally what people do anyways. So as a tool to help you kind of reach that. 00:02:59 - Speaker 1: Yeah, yeah. A lot of people end up making like Excel sheets and then sending them around. And it’s actually kind of funny, we noticed that it’s not just wanting to know who endorsed it, it’s who is against certain things. So when you see like, hey, this group is against it, you’re like, that’s surprising, why? And sometimes it takes like, hey, of the 10 ballot initiatives, 6 seem like everyone is in agreement, but then like maybe 3 are kind of like up in the air. And so you, those are the ones that you personally investigate. So it kind of just puts more time to the ones that you think are actually worth the the decision to make sure you get it right. 00:03:36 - Speaker 2: And tell us a little bit about your background. 00:03:39 - Speaker 1: Yeah, so I’ve done a lot of work in the tech space, but it’s not always specifically on the tech side. So my background is I came into tech via sales actually. So I was hired at GitHub as one of the first technical minded sales people, and GitHub was a very weird beast where there were no managers and you kind of like had to understand how to do a pull request to like even do anything in the company. So, I originally did Git Up sales, focused on the enterprise clients, but switched over to BD at GitHub, maybe my 2nd or 3rd year, as just a hugely undervalued piece of the business. 00:04:16 - Speaker 2: And I’ll briefly unpack that BD stands for business development, which I think itself is probably not a super well, in my experience, it’s not even a super well understood title slash function, so maybe you want to briefly describe what that is. 00:04:31 - Speaker 1: Yeah, absolutely. BD means so many different things. It’s kind of funny. I think a lot of startups tend to use BD as just another name for sales directly, like generating revenue and talking to customers. At GitHub, it was a little bit of a catch-all, so I was running sales partnerships where we partner with companies like Ubico and get more people using two-factor keys, but it was also partnering on the technical side. So working with companies to maybe build a plug-in, and specifically my charge was everyone who’s using the API helping them do their job better. And at the time it was mostly just like a ragtag group of maybe a couple 100 people using the GitHub API. They had a very open, very public permissionless API at the time, so people just, a lot of researchers, a lot of students, but then like a handful of companies who are trying to build a business. So my job was a little bit more. Focused on getting that group of people to be more successful, and the sales partnerships happened, they were just much less of a focus, and it was a small team, we maybe had 6 people max, so we kind of did a lot with a little. 00:05:40 - Speaker 2: And you had the same title at Abstract, if I’m not mistaken. Tell us about that experience. 00:05:44 - Speaker 1: Indeed, yeah, Abstract is a funny company. They do version control for design files, and BD at that company was much more around product partnerships and mergers and acquisitions work, M&A work. And so we didn’t do any kind of like sales partnerships. We specifically focused on anything that would help the product be a little bit better, and then kind of fielding the requests and inbound we were getting from interested parties around M&A work. And so that ended up being a lot of work when we got acquired by Adobe, but it was a pretty fun ride as well. 00:06:19 - Speaker 2: And it seems to me version control is by definition part of a tool chain, part of a stack, so those partnerships and integrations are crucial because that is the whole sort of reason for existence for the tool, and I assume there’s the technical integration, but then making those business partnerships where you’re doing something together, maybe that’s co-marketing, but maybe it’s also you’re trying to serve the same set of customers together even though you’re two different companies making two different products just from the outside it seems to me like that would be a crucial function. 00:06:49 - Speaker 1: Yeah, it’s definitely an important one. In both GitHub and the, you know, abstract case, these are part of a stack like you mentioned. People are considering entire tool chains, and so we’ve got to work nice with everyone and also try to help the group itself be better cause I think there is this constant struggle in the sass world of, you see companies who want to go single suite and company offer everything under the sun, like an Atlassian or Salesforce is another one of those. 00:07:16 - Speaker 2: Microsoft is the absolute king of this, right? You sign one contract, and you get a whole suite of mostly mediocre products, but it’s OK because they fit together and, you know, you could kind of buy one time and everything you need in the software world is kind of taken care of. 00:07:34 - Speaker 1: 100%. And then you see the opposite swing where it’s all best to breed, where it’s, hey, I really care about getting the best tool for this, even if it costs more. And we see companies swing between the two quite often. So whether it’s cost related or maybe it’s, you know, new leadership, it’s like, hey, we really care about developers, let’s break out of this like low cost tooling and now give them like stuff that they want to use. So in both cases in Abstract and GitHub we were kind of managing in the breast of breed world where we were working with partners who are, you know, all trying to serve similar and shared customers. 00:08:08 - Speaker 3: And an abstracts case, if I understand right, the design files are mostly probably opaque binary to some degree, and so they would not fit very well in a git style version control, and so that’s where the abstract steps in for that really special case of potentially very large, very binary. Difficult to diff files, is that right? 00:08:31 - Speaker 1: Oh yeah, absolutely. I love talking about this cause it’s like real deep and kind of amazing that as you exactly said the Git is more suited for plain text files and You know, there are things like LFS and Git that, you know, have pointers and allow big binary files to be version controlled, but it’s really hard. And so this is exactly what Abstract it, is that they saw Sketch was market leader, but they couldn’t solve this one piece around versioning because of these big binary blobs, and so they created an ingenious solution that actually did use Git on the back end and stored this enormous corpus of design information. And was able to kind of parse through the binary and pick up changes. So, at the time it was revolutionary, you know, there was literally nothing else that did this. And so they built a very strong business on that kind of like breakthrough in being able to take a workflow that worked with developers and apply it in the design world and give designers just like a huge amount of new workflow capability. You know, they could do branches, they could do merger requests, a lot of the same things that developers have used. 00:09:40 - Speaker 3: Yeah, that opens up so much more freedom. I’ve worked with designers running up against this exact same problem, probably, well, long time ago now, over 15 years ago, but it was, it was exactly this problem of there’s one blessed Photoshop file and if that gets messed up or there’s the classic version 1 version 2, version 2 final. Nightmare. 00:10:06 - Speaker 1: Final final, yeah, absolutely. I mean this is now obviated by all the web tools like a figma that, you know, are building versioning, just like a Google doc, you know, saving every stroke, but at the time when everything is desktop based, like, these are intractable problems, so it’s kind of interesting to see how The world moves into a different medium that solves it, but then introduces other problems, like now you’ve got multi-user collaboration real time, and that’s like, you know, a big headache, but also like a huge opportunity, so there’s always something fun to be worked on. 00:10:37 - Speaker 2: I believe that the developer workflow that is Encoded through Git and GitHub, which is a more asynchronous and the merger quest as a bundle and being able to look at diss. Obviously that whole thing is way out of reach for the vast majority of people in the world. But I do think a version of that probably can and should be part of almost every kind of creative tool, certainly for design tools, again, as you say, we do see that in the real time collab and the figmas and sketches of the world. I think you see this, one reason why Google Docs is really popular with writers is they have a really good versioning system or good versioning relative to the writing tools still. Pretty basic compared to what developers are used to, but where you can see new changes when you come to a document, you can look at a history, and critically, you can choose which changes to merge or reject, or have a comment this thread that is based on a change, right? That’s one of the biggest, I think, powerful abstractions in the mental model for something like Git, which is based ultimately on patches, which is you can talk about a diff as its own thing separate from the resulting code. And so that results in poll requests and then essentially code reviews and discussions around that. And I think probably most creative tools and fields could benefit from that, but the way those tools work for developers, it’s just way too heavyweight and complicated for most people. So, stay tuned. I can switch actually has some research tracks going on this, so I hope you’ll see some essays on the topic soon. And then I think you heard that time zones are one of the easiest and most fun things to do in programming, which is why you’ve worked on several calendar products as your own startups. Tell us a bit about that. 00:12:19 - Speaker 1: Oh yeah, my latest venture was called Eventbot, and it was a Slackbot that provided a calendar, basically behind every single Slack channel. And this is my 4th real calendar startup, and I’m just a glutton for punishment here. I think that In general, I like the calendar space because I think it’s interesting to build tools around how we use our time. Like I think if you can make that slightly optimized for people, it has a huge ripple effect. But I do think it is a brutal industry that where businesses are, you know, sitting in a large graveyard of failed to ups, so I’m not ignorant of how crazy that world is, but it was a fun project. I think we saw slack growing at a tremendous rate, you know, I’ve seen a lot of different approaches in the calendar world and me and my co-founder really saw like, hey, we could build this. tool that provides a really important niche within Slack, and, you know, maybe it can grow bigger than we think and we can, you know, put it into other areas, but we just sunset eventbot after 5 years of growth. It’s been a fun ride, but I do think that the business itself wasn’t able to sustain the amount of work required to keep it going. Like as you said, time zones are crazy. Little known fact, there are thousands of time zones, not even just the familiar ones. There are many Cities that choose not to obey daylight savings times, laws that are passed on a monthly basis that change how you have to calendar. So that part of the business is super boring and extremely frustrating for developers who have to try to keep up and make sure that they’re current. 00:13:58 - Speaker 3: I think calendaring is really interesting because there’s a built-in moat for any new business, and if you can swim across the moat and build a business, then to some extent you’re safe, but it’s so easy to just drown in the middle of the moat with all of the complexity of time zones and recurrence rules and invitations and It’s just a nightmare of Minutia that just drags you down by the heels. 00:14:33 - Speaker 2: That’s right. Well, I forgot you spent 5 years of your life working on Fantastic Cal. I did pretty successful kind of gooey calendar, so you’re very familiar with the pain there. 00:14:42 - Speaker 3: Yeah, my first startup was also a web calendar back pre-G Google calendar days, and I’ve made some pretty fantastic slash horrible decisions in learning that, just kind of walking in naively into the problem space and making choices that I instantly regret. Lots of bullet wounds and scars in that space. 00:15:06 - Speaker 1: Oh yeah, there’s lots of strange edge cases in the calendar world, you know, being able to even have a consensus of what is now, what time is today, like, these are things that when you’re talking to users across the globe that the internet affords us, have just so many edg…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/64-hiring/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: Here’s my number one tip for listeners of this podcast episode. The most unreasonably effective thing to do in recruiting is to move quickly, especially as a small company where you have the ability to do that. 00:00:16 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac, but this podcast isn’t about Muse the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here today with my colleague, Mark McGranaghan. Hey, Adam. And a fun little announcement here, we’re growing the Muse team, or we have grown the Muse team, I think it’s the right way to say it. So the designer storyteller position we posted a while back, we’re very pleased to welcome Linda Ma to the team as our 6th team member, and indeed we’ve also had some great candidates for what could be #7, that’s the local first engineer, so we kind of hope slash expect to have a similar announcement on that in the not too distant future. And this is what made me think it would be time to finally do an episode we’ve talked about for ages, which is on the topic of hiring or recruiting or perhaps team building. And this is something you’ve done quite a lot of, particularly a little bit of Hiroku and a ton at Stripe, and indeed you even have an article on your website, Thoughts on recruiting that I’ll link to, but maybe you can start us off by giving an overview of what you think hiring is all about and why it matters. 00:01:28 - Speaker 1: Oh, I have so much to say about recruiting, and it’s hard to believe we’ll even fit it all in close to one episode, but A couple of things I’ll say at this stage. One is that obviously the team that you build is gonna be the company that you build and the product that you end up building. It’s really the foundation. That I think is pretty obvious, but I think people often forget that. The other side of it is that this is a huge part of people’s lives. If you work, say, at 4 years for a company, that might be 5% of your mortal human life, you know, spent much of your waking time spent there. And maybe it’s a 10th of your career. So it’s a really big deal on both sides, and I don’t think that people treat it with the seriousness and importance and gravity that it deserves. Just kind of throw something up on indeed and, you know, respond to the emails or whatever. I don’t know. It just seems like such an important topic that really merits deep thought. 00:02:21 - Speaker 2: It is certainly part of the Silicon Valley culture to say hiring is, for example, hiring is job one for the CEO. That might be a phrase that someone might bandy about, but I would argue maybe some of that ends up putting a lot of emphasis on the quantity of hiring and the speed at which you do it rather than the quality and the quality not just of the candidates in terms of how they fit the company, but the team that you’re building and how it integrates and fits together and ultimately can. Do what you’re there to do, which is, you know, build the product. 00:02:53 - Speaker 1: Yeah, I think a big theme of this discussion is going to be holistically thinking about recruiting, hiring, team building, and zooming out a little bit, and it’s not just about all the little tactics, it’s really easy to get to zoomed in on that. We got to keep in mind the goal of having an effective productive team, and considering all the things that can lead up to that. 00:03:14 - Speaker 2: I think an important part of what we’re talking about here as well is that we’re obviously talking largely about hiring the technology industry, which is where all our experience is, but I think an important part of it is hiring creative people to create something that’s often fairly novel in the world, and so you really need, there’s the whole mission driven concept and being aligned and sharing values, all of these things I think are an important part of it. That’s one piece of it is I think you really need to get people who are going to put their spirits into it in a way that It’s not just do they have the skills, it’s a do their passions line up with the things the company needs. And a related thing is the immense privilege we have being in this industry, which is it’s a very in demand field and so the people who are being hired side of the equation, they have a lot of options. Not only are they well paid, but they have the luxury, you know, if you’re good at interviewing and have the right CV and everything like that, you may be able to get offers from several places. So the hiring manager is often not just kind of this doing this transaction of here’s the work that needs to be done, here’s the skill set, and here’s the compensation. But actually there is an element of getting them to join your club, perhaps getting them to join your cult, buying in on the mission, believing in it in a deep way. And I’m reminded a little bit of this 80s movie Ghostbusters, where you have the original founding team of Ghostbusters, who are these kind of kooky types, or at least some of them are these kooky types that have all these beliefs in the supernatural and the occult and so on. At some point they realize they need help and they go to hire someone new and, you know, they’re basically asking interview questions about, what do you believe. This and this and this, and he just says, look, there’s a steady paycheck in it. I’ll believe anything you want. That’s probably not what you want for creative work. You want someone who is going to buy in because indeed the things they care about and working on in their career, perhaps things they’ve worked on in the past or their personal passions match up to some degree with what the company’s mission is. 00:05:16 - Speaker 1: Indeed, one of my little recruiting nuggets is that the primary challenge with recruiting in this technology industry is attraction, not filtering. I think people go to filtering things like, what are the interview questions and what are the criteria that we’re gonna use to knock people out of the process because it’s more inwards focus, it’s more about you and what you’re doing in the office day to day. And also because I think people are keying off of companies like Google, of which is a very small number that have a legitimate filtering issue where they have a huge number of people applying. The challenge for the overwhelming majority of software companies is that people don’t apply to your job, they don’t even know about it. That’s why I think this attraction problem is so important. 00:05:55 - Speaker 2: Well, I thought a good way to structure this might be to talk through the hiring process we use at Muse. Now, Muse, importantly, is not a growth oriented startup, but I think we do need to attract in your wording here in the same way that a faster hiring company would, and this is a process I think you and I have used a bit at Hiroku. I’ve used in different companies and it’s kind of what we use in Muse. And not to be too process focused, but maybe in talking through it, we sort of reveal the tips and tricks, the values, the approaches, the painful lessons we’ve learned over the years. Maybe also worth as a glossary here, kind of defining a couple of terms that I will certainly come back to a lot. One is team. And that the team of people that you’re trying to put together to again be sharing those values and having work in chemistry and a sense of creative trust and the ability to make commitments to each other and keep each other accountable, that’s a key part of this. You’re not just trying to hire individual people, you’re trying to build a team and each of those people needs to be integrated into the team. And I was like the anti- example of a team, which is something like US Congress. The members of Congress may be colleagues, but they are not a team because they really don’t have the same, many of them don’t share values or have the same end goal, and so it’s a contentious sort of finding of constant compromise, but I think a good team is one that does share more values, goal, mission, and so therefore you’re getting to great, great outcomes. The kind of team is one word in there. And then two others that will come up a lot, I think is manager or hiring manager. And actually doing a whole podcast on management is another topic that’s in my backlog somewhere, but at least for the purpose of our discussion here, take a hiring manager and then the person who not only figures out who should come into the team, but also helps them be successful is a big part of this equation. And then the job description is the other one, and we’ll probably start there. So a clear written description of why you want to hire, what problem is being solved, and what candidate would look like that would kind of fit that slot. 00:08:05 - Speaker 1: Yeah, it’s a good baseline to have. So, where does the process start for you? 00:08:09 - Speaker 2: Yeah, well, number one is the hiring manager writes a job description. And obviously that starts with whoever is going to do the hiring kind of recognizing a need. So this is why it’s important to, to my mind, label a hiring manager who is a single owner for this, as someone who’s identified. We need someone on the team and we’re going to figure out exactly what that looks like and do the filtering, both the attraction and the filtering that you mentioned, but also the onboarding and helping them be successful on the team. But that kind of clarity of here’s a single owner for this project because it really is a project and they may take input from a lot of sources to create the job description, which is a written thing you’re going to post somewhere that tells people what you’re looking for in the role and about your company, but that person is going to really own that whole process. 00:09:00 - Speaker 1: Yeah, and I’m a really big fan of having this alignment between the person who’s eventually going to be responsible for the person’s success on the team all the way back to writing the job description and sourcing the candidates and running the interview process. I’ve observed that in large companies, this often gets broken up among a bunch of different people. Sometimes, you know, for The defensible reasons, let’s say, but you have the recruiter and the executive, and the group manager and the manager, and the saucer, and the zillion people, and no one’s really responsible, a candidate’s bouncing around through all these folks, and you don’t get a strong, coherent, unified vision for what this job is gonna be and why it’s awesome. So I think we can get away with it, having a more unified approach is the best. 00:09:43 - Speaker 2: Yeah, I’m not a big fan at all of kind of recruiting in HR, playing a big role, especially early screening. I I understand why that specialization makes sense. I’ve worked with great recruiters and great HR people who are very good at what they do, and certainly they take the weight off of the team leads or hiring managers that have lots of other responsibilities. They have their own specialized skills in some cases for just Dealing with people and following up correctly and so on, but yeah, some more unified ownership, I think creates a better experience for the candidates, and I think it is more likely to make the whole process kind of be successful. What does a good job description look like for you, Mark? 00:10:23 - Speaker 1: For me, it’s effective in convincing the best candidates that they should begin a conversation. And let me contrast that to what I often see in job descriptions, which is speaking to sort of the median candidate and giving them as many reasons as possible not to apply, right? You don’t paint a picture of why the job is compelling, why the teammates are going to be great, what they’re gonna learn, and you get this whole laundry list of, you know, so-called requirements, many of which are not even useful. So when I’m writing a JD I’m thinking. Maybe I have a handful of people who are ideal archetypal candidates. Why, when they read this, are they going to be interested in speaking to us? And once they speak to us, you know, that starts a whole another part of the process and we can almost forget about the JD in a sense. But you just want to get that first conversation. So it’s again, it’s about attracting the right candidates and you don’t need to really care about what we candidates think, and you don’t need to care too much about strong people applying who aren’t exactly the right fit. That’s a good problem to have. You’re just trying to get some initial attraction from strong candidates. 00:11:27 - Speaker 2: Yeah, being specific so that when someone who is the right person reads it and says, this is me, and feels compelled to apply, but also not so specific that you, as you said, repel people. The requirements section in particular is a dislike of mine where it’s for example 3 years of experience with a particular technology, but I think it’s really a certain set of characteristics in the person’s personality and the kinds of things they’ve worked on in the past and what they’re drawn to and the types of problems they’re good at solving and certainly for a technical role technology experience is first of all important to talk about. But secondly, helps people know what the position really is and helps define it. If it says you’re a great swift engineer, then you know that’s going to help clarify a lot, but saying you have exactly this many years of experience with a particular technology in the Apple ecosystem is a little bit too, I don’t know, just leads to disqualification for not a good reason. But then you always have this balance between, you don’t want to be too vague. Because then it doesn’t speak to anybody, but if you’re too specific, you disqualify potential good candidates, and in a way, you don’t know who you’re looking for, right? You’re trying to like put this beacon, this attractor out into the world and you have a vague idea. Hopefully that idea is based a little bit on the exercise of dream candidates. So this is something I like to do, which is, OK, if you could get anyone in the world, even someone who’s completely ungettable because they’re a celebrity or they’re busy with their own thing or whatever. Who to be. And if you get 345 of those examples, and you look for attributes they share, and you write down those attributes in the job description, that’s very likely gonna, in my experience, do the job you described, which is help attract those great candidates without having the specificity that repels people for no reason. 00:13:19 - Speaker 1: And the flip side, by the way, of the industry not taking this recruiting process very seriously is that most jobs and JDs are actually not good. So if you have a really good job, if you’re offering a genuinely good opportunity and you write a really compelling JD, you can actually pull a lot of people out of the woodwork with that. 00:13:40 - Speaker 2: Absolutely, I always considered a good sign when we get people applying who say, I’m happily employed, I’m not looking for a new thing in any way, but this was just so interesting. I just had to talk to you, something of that nature. 00:13:56 - Speaker 1: One other thing I’ll say about JD, I do think the main role is outwards facing attraction. JDs also are helpful internally for getting the team on the same page about what this person is going to be doing. We were working through this recently with the local first engineer. We decide, OK, is this person gonna be doing protocol design and distributed systems, or is it more like working on the clients, the iOS client or the JavaScript client, or is it more like a just a pure back and go engineer or is it some linear combination, or is it choose your own adventure? And just having that conversation is good. And like t…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/65-trademarks/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: You can also be notified just based on an algorithm, you know, if somebody files something that’s similar to your trademark to trigger a notification to you. The interesting thing about the trademark office, at least from a government perspective, is it’s the most government 2.0 out there in the sense that the data is publicly available and can be downloaded every single day. 00:00:24 - Speaker 2: Hello and welcome to Meta Muse. M UUE is a tool for deep work on iPad and Mac. This podcast isn’t about Muse product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGranaghan. Hey Adam. And we’re joined today by Josh Gurbin of Gurban Intellectual Property. 00:00:42 - Speaker 1: Thanks for having me, guys. 00:00:44 - Speaker 2: And Josh, I understand you have 4 kids. How in the world do you manage life work balance with that and being a business owner? 00:00:51 - Speaker 1: That is incredibly difficult. I will say that the plan was maybe not to have as many kids initially, but these are the things that happen as life goes on. And one of the great benefits I have is that I get to work from home every day. So I don’t have a commute into the office or home from the office, so I can wake up, get to work, and You know, when the kids get home from school, I have a little time, but, you know, I’m not wasting an hour or 2 hours a day commuting to and from an office in a big city and having that time back is really the critical element I think in making it all work. 00:01:23 - Speaker 2: That’s huge. Now have you found some good techniques for communicating boundaries around your office slash, you’re on a call or just need to focus, especially, you know, I don’t know how old your kids are, but the younger they are, the less they understand, you know, closed door means you can’t come in. 00:01:39 - Speaker 1: Absolutely, so in my house we actually have an office, you know, that I work from that’s dedicated for me and everybody understands that the doors closed, you know, you just don’t come in, I’ll come out when I’m ready, and luckily, you know, when you work from home and you talk about those boundaries with your kids every day, they really understand what you’re doing. Now, of course, there’s gonna be a situation here and there where they run in and They probably shouldn’t be, but the benefit of COVID is so many people have had to work from home and deal with that now that it’s not unusual for anybody to kind of see a kid running around on a call here and there, so it’s almost an enduring quality these days, so I find it works pretty well and for the most part, you know, we’re able to sort of separate in our house. 00:02:17 - Speaker 2: Absolutely, I almost wonder, yeah, every time my kids run in and jumps in front of the screen and everyone sees her, you know, it’s obviously always like a very positive reaction, but I almost wonder if that’s a positive reinforcement for what ultimately is not a good behavior, which is, you know, violating the boundary of the closed door or the workspace. But yeah, then you can’t resist it. Everyone’s just entertained to see an unexpected cute face pop up on the screen. 00:02:42 - Speaker 1: And honestly, if you have kids, you appreciate what’s going on and you understand what’s going on, and I think that that’s something that, you know, to me it doesn’t bother me if I’m talking to somebody and their kids budging. I like to see what their life is like. I like to see that they’re a human being too, right? And I think that that humanizing aspect of things can even make relationships stronger between people. So I personally have no issue with it, and I think if somebody does and they’re probably got ice in their veins, you know, it’s. 00:03:08 - Speaker 2: And tell us a little about your firm and your background. 00:03:12 - Speaker 1: Yeah, sure, so I started the law firm in 2008 in the middle of the Great Recession. I had a steady job, a good job at the time. I was 2 years out of law school and everybody thought I was absolutely crazy as 27 years old and they’re like, you’re gonna start your own law firm? I mean, most people don’t want to hire a lawyer and it looks like he’s 12 years old and I definitely looked like I was 12 years old at the time, but I said, look, I can offer pretty low-cost service and I’m not gonna have any overhead and I wanna really be out on my own. I’ve always wanted to have my own business. And basically started by using Google AdWords and going out there and putting up a website and slowly but surely got clients and If you’re just building brick by brick day by day, ultimately you build up some clients, you get some repeat and referral work, you continue to take a new work and slowly but surely you grow a law firm, and now we’ve got 13 employees, we file around 1000 US trademarks every year plus hundreds of trademarks in other countries around the world. So it’s been quite a ride and just something we’ve built very methodically and slowly over the last 14 years. 00:04:15 - Speaker 2: Nicely done. I feel with a services business, which I for a few years was a software consultant, and the common wisdom there and certainly reflected my experience was you get business through referrals, essentially through your network and ideally clients that refer you to other ones, but they tend to be all word of mouth. But we found you. Because you have a good website and I basically just Googled US trademark when we were thinking about filing for Muse and now we have a multi-year business relationship. I don’t know, is that unusual that we came in that way, or is this kind of reflecting a new reality of the internet world which is you can actually essentially get randos from the internet that come to hire you for your service. 00:04:57 - Speaker 1: Well, yeah, absolutely, and that was a lot of the disbelief that I had amongst the legal community because lawyers, you know, they tend to be really reticent to adapt to new technologies and new techniques of advertising and things, and everyone said, who are you gonna find online that’s looking to hire a lawyer? Who are you gonna really get? And well, obviously, you know, we’ve gotten some really good clients, you included and One thing that we invested in very early on was search engine optimization. So you likely found us through an organic search and not necessarily an ad. I will say that in my experience, you know, the clients that come to us when we were doing the Google ads, which we don’t really do anymore, were harder to kind of parse through all the leads and finding sort of the good. Ones in that bag of leads that would come in every day. But because we have such a great organic presence and work really hard on that, we find that the clients we obtain from that presence tend to be really, you know, great clients, and we’ve built a business that way. I will say probably now, to grow a service business, I certainly agree you need the referrals because it’s very hard. You know, there’s a lot of work that goes into building a new relationship with a new client that’s found you online and has their own suspicions about you and building that trust factor is really challenging. But if someone comes in through a referral and it’s a warm referral, they have the trust already, they’re like, oh, this person has worked with Josh, they know his firm, they trust him, I’m gonna trust him, right? And so there’s a lot less work that has to be done to build up that relationship and that’s really what’s allowed us to grow is that warm referral business that we have. 00:06:24 - Speaker 2: One thing I noted right away on the embrace of technology side is you had a calendly link or some kind of automated form for basically asking for your time, asking for a call, and I think I’m not sure how common that is nowadays. It’s very, very common in the tech industry, but this. It was 3 years ago or something like that, and so I was quite impressed by that and it seemed to signal that you were embracing technology to make lives easier for everyone, and that implied to me that we would be sort of compatible in terms of working together, a working relationship. 00:06:55 - Speaker 1: That’s so interesting to me to hear that because I have gotten mixed feedback on that Coly link over the years. Some people really hate it. They take it as an insult that you won’t take the time to schedule a call with them, and I’m just shocked because I’m like, well, how many emails do we need to trade to find what time works for you and what time, and this is just you go in there and you just, you know, yeah, I mean I think that’s a nice. The thing about working with people in tech is that you appreciate those tools and, you know, we do offer a lot of our services at a flat rate, so we are incentivized as a law firm to be more efficient, and that is actually, you know, the reverse of the way a lot of law firms think, because a lot of law firms are like, well, we want to be as inefficient as possible and build as many hours as we possibly can to get this task done, and we’ve always been designed of, we need to get this done as quickly and as good as we can, but we need to get it done as quickly as we can. When you’re focused on that, you look at all the different tools that are available and you start to use them because they’re really helpful in keeping your time down and letting you move through projects. 00:07:51 - Speaker 3: This is very interesting to me. So, for the listener context, Adam has sort of reached out and established the relationship with Josh, so I wasn’t involved in that, and I wasn’t aware actually Adam, that you had reached out sort of cold over the internet, and my experience with almost all Lawyers and accountants and similar professional services firms is that they basically don’t talk to you unless you have a referral. They don’t quite come out and say that, but that’s really the MO of most folks, but I think it’s notable that Josh and I think the law firm that we worked at, we both found through their online presence basically and reached out, and then our accountant we’ve known for like 10 years, so that’s a different case, but it is one little data point in the changing world of professional services. 00:08:30 - Speaker 1: Yeah, it’s interesting to hear. I mean, I think that it depends on the size of the professional services firm because a lot of the firms are set up to have these really significant overheads, and they have a very developed client base that they’re billing every year, and these are retainer clients and they have these very set budgets. So when they take on somebody new, that new person needs to have a certain budget in order for it to make sense for that firm to take on. And where we differ is we have a very low overhead structure and we’re actually focused on serving. A lot more diverse of a client base and let’s say 100 big clients a year. We’re focused on serving 1000 smaller clients a year. And to us, that’s a great benefit because if one client for some reason leaves, we’re not looking at having to lay people off or having a huge loss of revenue, you know, we still have the 999 other clients that year that are gonna be, you know, keeping us afloat and keeping the lights on and our people paid. And so when you’re not reliant on these like large whale clients, then you are more apt to really want to take in, you know, new work every single day because you are relying on more or less the volume. 00:09:38 - Speaker 2: We went through something exactly like that with our software consultancy, which is we got some. Bigger projects, in particular, one big client and we had to staff up to serve their needs, but then when things changed with them out of the project or whatever, and then suddenly we’re scrambling around to find enough work to keep these folks fed and so yeah, I mean, it’s of course it’s always the case that professional services and you know it’s kind of like a scaled up version of freelancing, which is feast and famine. That’s right, but the more you can diversify and spread out a little bit. But yeah, you get that client that comes in and, you know, basically is well has like exactly as he said, and that’s it’s really compelling, that’s how a lot of services businesses do what they do. 00:10:19 - Speaker 1: Oh, for sure, and I mean you know we had in the last 2 years, we had 3 or 4 of our largest clients get acquired, and when that happens a lot of times you lose the trademark work because the business that’s acquiring them is much larger and has their own lawyers already and so, you know, we have to be prepared that even when we build up and work with a particular Client and they become a larger client, they’re eventually gonna leave. So you have to always kind of have what you call a farm system of clients you’re developing and hopefully getting into the next big client to take the place of the one that will eventually leave for one reason, either through a sale of the company or they get so big that some other lawyer poaches the work or whatever it might be. 00:10:55 - Speaker 3: Yeah, I wouldn’t be surprised that even if you don’t have outsized clients in terms of work, you probably have some clients that give you an outsized amount of referrals. I’d be curious if that’s the case. 00:11:06 - Speaker 1: Yeah, you know, actually other lawyers are our best source of referrals because a lot of other lawyers don’t have a specialty in trademark law and they’ll get a question from a client about a trademark, and there’s this ethics rule that applies to all lawyers that you can’t do work for somebody unless you really feel competent to do it, and if you’re not feeling competent to do it, you might have to charge your client to get competent, whereas they could just call us and we could do something really quick and easy for their client and the client gets great customer service. And at the end of the day, the lawyer doesn’t lose their client because we’re not looking to take, you know, somebody on for more than the trademark work. So when we start working with our lawyers and other law firms, they’re like, wow, this is great, we can send these things over to Gurin and they turn it around and get everything taken care of and the client’s happy and they’re staying with us for their other corporate work or whatever it might be. And so those law firms and lawyers tend to be our best referral source. 00:11:59 - Speaker 2: Well, that’s certainly a benefit of the tight specialization that you have, and maybe that is a good transition into our topic today, which is trademarks. So maybe this is a slightly surprising one for our listeners who are used to a lot of our focus tends to be on design, product, tools for thought, research, things like that, but at least one of my goals with this podcast is really to document all of the aspects of building a business that Mark and I and all the others on the Muse team are going through here and the trademark is. One corner of that, but I found a surprisingly intriguing and intellectually engaging one. And just in our conversations, Josh, just on the phone working through our case of getting our various trademarks filed, I’ve been just fascinated by the mechanics of it even past what’s necessary for the purpose of doing the project, so I hope we can share that with our audience here. 00:12:49 - Speaker 1: Yeah, absolutely. That’s my everyday. 00:12:53 - Speaker 2: Now of course, I’d like to tell a little bit about the Muse journey in our trademarking and why we’re motivated on all that and so forth, but we always like to start really at the beginning, which is just definitional. What is a trademark? 00:13:06 - Speaker 1: Yeah, so a trademark is a source identifier, meaning that it identifies the source of goods or se…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/66-business-of-apps/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: I remember the last time we did a paid upgrade, we had a feature done for almost a year before we actually shipped it because we knew it’s such a huge feature that will bring in new customers and make it easier for them to understand why they have to pay again. 2.5 years ago, we switched to a subscription-based business model. And this is also switching company development culture that you suddenly have to ship updates or features more often. 00:00:32 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac. But this podcast isn’t about Muse product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Adam Wulf. Hey, everyone. And joined today by Marcus Mueller Sihoffer of Mind Node. 00:00:50 - Speaker 1: Hello, thanks for having me on the podcast and greetings from Vienna Austria. 00:00:54 - Speaker 2: Yeah, and you’re in Vienna, and this is a city that’s known for, let’s say it’s classical music history. Mozart is a certainly a name that springs to mind. Is that something you ever took advantage of? 00:01:05 - Speaker 1: Oh yeah, when I was still a student, I really like to go to the opera, of course they had those really cheap standing room tickets back then. I think they still have it, sorry, but nowadays, yeah, I have kids now and well the business, so I hardly ever find time for that, unfortunately. 00:01:22 - Speaker 2: Well, Wulfstaller is about to head off to university, so that’s gonna be lots of room in your life for opera after that, huh? 00:01:29 - Speaker 3: Yeah, that’s right. I just need to make the 1.5 hour trip downtown to go see it. So that’s my other thorn in my side. 00:01:39 - Speaker 2: Well, before we dive in here, just a quick housekeeping announcement. The Muse team, together with a friend of ours named Arun, have put together a little website. It’s at infinite canvas.tools, and I’d like you all to check it out. The idea here is to kind of give some definition to this category. We talked with Steve of TL Draw a few episodes back about Infinite canvases and I guess we were inspired enough by that. We felt like that a standalone site that helped define the category better would be worthwhile to all of us. And indeed, Marcus, this is an interesting tie in with your history a little bit, which is, I believe you worked on a project of that exact name some years ago. 00:02:18 - Speaker 1: Yeah, that’s right. Back when I was still at university, I did a student project. And later on, it’s also turned into my final thesis, in fact, where I created an app that was called Infinite Canos and it was highly inspired by a comic book or graphical novel by Scott McCloud. Scott did two interesting books about comics. One more general book describing what comics are. And a second book describing how he would reinvent comics for the new digital age. The book was also called Reinventing Comics. And in one of the later chapters, he described the concept of infinite canvas as a tool or method to bring graphic novels to the digital space, in fact. And as part of my studies, I created an app that allowed you to put graphics on an infinite canvas more or less. And then put a navigation area on top of that. So that allowed comic artists to create interactive comics that they could lay out and then present in a that place to to their readers. And unless other kind of student project, this project actually found some comic artists who created their own comics and their own graphic novels of that it was kind of cool. 00:03:39 - Speaker 3: That’s really interesting, so it’s not just an infinite canvas, which I think of as A very general just giant space, but there’s a specific navigation format or navigation structure that was built into it as well. Am I understanding that right? 00:03:54 - Speaker 1: Yeah, when we considered that at first, what we wanted to do, we had concerns that if you just provided an infinite comes to the readers that they would have problems navigating these cameras. And so we came up with navigation layer on top of that that allowed to predefine a certain path you could take around this canvas. And you have to compare it to a typical comic, which is laid out on a piece of paper, and then if you bring that to the infinite canvas or to a canvas that’s infinite, you can lay out the panels all over the place you would like to do. For example, there were comics that were just side scrollers or comics that took in all different directions. Unfortunately, many of those projects are no longer around because back then I used a chalet for the viewer part and Chalet is more or less separateated and. And later ported it to Adobe Flash and that’s also unfortunately not really available. 00:04:49 - Speaker 3: It’s the never ending story of technology, I think. 00:04:53 - Speaker 1: Oh, that’s true, yeah. But if you like, you can still go to infinite canvas.com and see how the app actually looked like, but I fear most of the projects are probably no longer available. 00:05:04 - Speaker 2: Marcus here, the CEO and founder of Mind Node, which I think of as the quintessential or most canonical mind mapping app. It’s been app of the day, it’s been around the app store for a pretty long while. I think of it as a well respected tool for thought from before that term was sort of popular or experienced the modern resurgence that it has. But before we get to talking about my Node, I’d love to hear a little bit more about your history, maybe what happened in between the time of that student project and thinking about comic infinite canvases and the creation of the business you’re working on today. 00:05:41 - Speaker 1: Yeah, let me go a little bit further down my history. I have a major in computer science, and back then the computer science curriculum was very, very general in Vienna. There we had many courses in mathematics, computer algorithms, computer graphics and stuff like that. And going into the study, I was never really sure what I really want to do. My vision was, oh, I just wanted to do something with computers because I like games, so computers are the things I wanted to do. And having this exposure to all those different parts of computer science allowed me also to experience human interaction design. And this is something I was never really interested in before, but throughout my studies, I kind of always had those intersections with that. And I also had, what’s kind of interesting, I had a course on next step. Which kind of showed me a new way to use a computer, which was kind of different from the Windows side, I only knew. So with the exposure of having experienced the next step computer and then also my the growing interest in human interaction, I started considering getting a Mac, and this was the time when Steve Jobs announced the iMac G4, which was this kind of cool looking computer that looked like a stand, which I have still somewhere in my office. 00:07:01 - Speaker 2: Is that the cube? 00:07:03 - Speaker 1: No, the tube was before that, that was the T4 tube. It was the 2nd generation iMac, that’s where you had this kind of round stand and then you had the flat panel the hinges come out of that. 00:07:15 - Speaker 3: Oh, that’s right. Yeah, that was a beautiful machine. 00:07:17 - Speaker 1: Oh yeah, it kind of looks very similar, or at least the hinges look very similar to the studio display if you get the one with the moving, where you can move the display up and down. So yeah, back then I really had nobody around me that used the Mac, so it was kind of jumping into cold waters. But if you think about decisions you made in your lifetime, that was definitely one of the better decisions I made and it was just one of those feelings that I follow that, wow, that’s probably. Yeah, that’s just a feeling in there, but if I do that, it feels great. And this is when I kind of left the Apple platforms. This was also the time where the iLife apps were really popular. If you think of iTunes, iMovie, IDVD and IAB, for example, they were great focused apps that did one job really well, and for the, they were designed for this one use case. And this was kind of influential on me. And then there was a second part, it was very influential, and that was the upcoming of ID Mac developers. If you think back, there was delicious library or Net Newswire. So, after I wasn’t really sure what I wanted to continue to do, but having those people show what is possible, creating your own small Mac software studio, that’s kind of something that really inspired me to try to do the same thing. 00:08:40 - Speaker 2: So the MMA G4 was introduced, what year do you remember? 00:08:44 - Speaker 1: 20 years ago. 00:08:45 - Speaker 3: Wow, that long, yeah. 00:08:46 - Speaker 2: And then how long between sort of that device, seeing these indie apps, falling in love with the Apple platform, and the founding of what would be the company that would make my Node. 00:08:58 - Speaker 1: I wrote the first one of mine to note in 2007, so it’s now 15 years since I started the project. 00:09:07 - Speaker 2: Wow. And, yeah, give us the elevator pitch. What is my note? I’ve already perhaps tipped it off a little bit, talking about mind mapping. 00:09:16 - Speaker 1: The awesome thing about MO is that I didn’t create the app because I thought, oh, cool, mind mapping app would be a good idea, but I was kind of stuck in the infinite chemist project we talked earlier because I had this big picture of few idea that, OK, I have this app. It’s kind of popular in this niche area. But let’s try to bring this to a more. Broader audience. Just imagine having an infinite canvas where you can show your presentation, that’s something that’s was unique at the time and I thought, oh, that could have potential, but as it’s always with great ideas, you have too many of those and you don’t have a clear vision on what you really want to do in the end. So after coding for a while, designing for a while, I was kind of bummed out. And looked into techniques that would allow me to bring back this focus, bring back or allow me to really discover what I really wanted to do. Did a little bit of research and discovered mind mapping and well, I’m a computer engineer. I like coding. So the first thing you do when you come across a new concept, you want to do it yourself. So I want really great apps back then, mostly ports from Windows, I decided, oh, let’s look what Apple is doing with the I work apps, what all these other indie developers do. Just try to do a tool that does one job really good. And I started a prototyping phase. I decided, OK, let’s try it for one month, see how it turns out, and then I can still decide if I want to go back. To infinite canvas or if I want to resume it I know. 00:10:51 - Speaker 3: It’s really interesting. I feel like that’s where Almost all good products have that same kind of a route, where they’re solving a very specific problem. It’s not just building neat software, but you are building neat software to actually help you think better, to help you do something better. It had a very specific purpose for you. Sounds like that gave a lot of Vision and direction for you early on. 00:11:15 - Speaker 1: Yeah, I always feel that the best features in Myno or and other apps are the features that the developer itself uses. So if you develop a feature just because a customer wants to use that, you will never create a great feature, you will create a decent feature. But if you really are the user and the customer of the app, then you really are behind the feature. You understand how the feature works. You just don’t have some description of how the feature should look. Or behave, you actually lift the feature, you know all the ins and outs, you really know in what edge cases you can run and and those are often the features that turn out really great and awesome. 00:11:59 - Speaker 2: And originally this would have been for Mac because the iPad didn’t exist. Am I right about that? 00:12:05 - Speaker 1: Yeah, I think the iPhone might have been announced by the time I started creating my Node, but I think that was way before the SDK. So I started initially on the Mac. This is also where I had the most experience. And even after SKN was announced, it was kind of, ah, I did some experiments, but it was kind of hard to create something with an expanding or infinite canvas to the iPhone because the API wasn’t really designed that way. So I started with doing. The Mac version first and then later try to bring that to the iPhone platform and then also to the iPad. 00:12:41 - Speaker 2: And I first saw it on iPad, and I think this was circa would have been more like 2017 or something when we were doing tablet research back at in and Switch, but one of the things I was struck by was how just beautiful and good the iPad hardware was, particularly when paired with the pencil, which was relatively new at the time, and I went looking for really good quality iPad apps, and I was just shocked how few of them there were. So many were just iPhone ports, in many cases they were scaled up or, you know, just like in a letterbox thing. And so, from my perspective, it felt like an app that just could have been born on the iPad, it was made for iPad, but maybe that also to me is the connection in my mind between a tablet is such a great device for open-ended ideation, which indeed is what mind mapping is. You can sit back on your sofa, you can take it to the coffee shop, something like that. So it’s interesting to hear that that was a very latecomer to this product. 00:13:42 - Speaker 1: So when we decided to do the iPad app, it was just a 1 to 1 part of the iPhone app. We actually, when we released our iPad app, I still had no access to a real iPad back in the days because they were only released in the US and not. In Austria, even had one of our customers send me one of the first iPads so I could actually try and use the app on the iPad. But you always have to keep in mind an iPad app also has to be a good iPhone app because you can always resize the app itself to be as small as an iPhone on an iPhone device. So that’s all I think the real big. Challenge of doing a great app for all free Apple platforms or major Apple platforms that you always have to keep in mind the app could be launched or could be a size like an iPhone, an iPad, and a Mac. And I think iPad and Mac are starting to converge a little bit, especially now with iPad S16, but you still have to keep those tiny iPhone screen in mind. 00:14:42 - Speaker 3: I’m really curious to hear how difficult it was to make that jump to iPhone, and then eventually to iPad, cause as I recall, the Mac APIs kind of in the late 2000s versus the iOS SDK were pretty dramatically different, and then they’ve kind of congealed lately and merged together in a lot of ways, but at the time, Pretty separate. Is that just a huge effort and what were some of the risks or thoughts in your mind as you Expanded into new devices. 00:15:15 - Speaker 1: Creating the first iPhone version had several challenges looking back. Definitely very restrictive hardware and uh a really a huge problem of fitting everything into memory and the app getting killed if you use too much memory was always a kind of an issue, especially if you look at the technical side, we tried to use internal layers back in the time. And those had really issues with fitting in a memory and if you imagine how a very graphic intensive apps like my not has to do it, we have to use very large layers to draw all of our branches. So that was a really challenge. Another challenge was actually text because back then, the iPhone only had simple text, so there were attributed strings are similar. So then we ported my the iPhone, we actually had to define a new and custom file format t…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/67-dynamic-documents/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: As software developers, maybe we go towards building a GUI with specialized inputs and forms and controls too soon, because it’s so much easier to explain to the computer what the user means if they use a specialized input tool like a button check box and so on. But if that weren’t the case, if it’s easier for the computer to understand what you mean as you’re typing in your note, then suddenly text input is the primary thing. 00:00:32 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac. But this podcast isn’t about Muse product, it’s about the small team, the big ideas behind it. I’m Adam Wiggins, joined today by Jeffrey Litt. Hey. And Max Schoening, great to be here. Now, the two of you are working together with some others on an ink and Switch project we’re gonna talk about today, but first, I understand that there’s some cooking adventures going on in the lit household. 00:01:02 - Speaker 3: Yeah, so I’ve been trying to make my own stock lately. I’ve been reading this incredible book that someone recommended to me on Twitter called An Everlasting Meal by Tamar Adler, and it’s all about how to use leftovers and just like random stuff in your fridge to cook both as a way of not wasting, but also just cause it feels good. So I’ve been, you know, throwing random like carrot tops and stuff into a pot, and it feels really fun. That’s my recent cooking adventure. 00:01:29 - Speaker 1: Inspired by, we’ll get into it a little bit later with the project too, but partially by Jeffrey’s cooking. I’ve also started taking cooking maybe a little bit more seriously than before. Like I think one of the things that sort of distinguishes the amateur from someone who’s more seriously involved in something is consistency and my cooking was never all that consistent cause the loop of how frequently you repeat a dish when you’re just cooking sort of for fun is very long, right? So the learning is slow, so I’ve been getting into sous vide cooking. And just eating way more steak slash anything you can sous vide that I would like, but at least the results are getting better. 00:02:11 - Speaker 3: I’m a sous vide fan as well. It’s a major cheat code, I find. Everything is perfect every time. 00:02:17 - Speaker 1: I wish that had been my experience too. 00:02:21 - Speaker 2: Yeah, consistency and repetition, yeah, short feedback loops. I was inspired by a book, I think it’s called the Food Lab, where basically the author does some, call it like. Amateur science in the sense of taking common cooking claims, like should you salt meat before cooking it, or is it better if you don’t flip it, or you only flip it once versus twice or something, it would essentially just cook several side by side, varying this one thing. And then do a little informal taste test with his, you know, housemates or whatever, and sort of like try to answer that question, and many times found out that, or at least had the finding, let’s call it, that things that people swore by didn’t really actually make a huge difference in the outcome, but that idea for myself, I think even our Mutual friend and colleague Peter Van Hardenberg introduced a version of that in the Hiroku offices when he would do a little coffee workshop and essentially like brew a cup of coffee with several different approaches, you know, here’s the Chemex, here’s the French press, here’s the, and then you could taste them side by side and have new appreciation for the way these different techniques change the taste of the same source bean. 00:03:34 - Speaker 3: Yeah, I love that mindset. I think what I see as the challenge at home cooking is, you know, to bring in some of that idea of getting better and being a little rigorous without making the whole thing too overcomplicated and kind of perfectionist. There’s some aspect of amateurism and just having fun with it, that’s sort of the whole point to begin with. So I think that’s a fun balance to strike. 00:03:57 - Speaker 2: So longtime listeners of Meta Muse will know that we’re shaking up the format a little bit here. This is our first time with two guests. It’s usually me and Mark as co-hosts along with one guest, and this is partially my theory that it’s a little hard for listeners to adapt to two new voices, but in fact, you two are not new to our guests potentially. Max, you are one of our very first guests all the way back in episode 8 when we talked about principal products. And Jeffrey, you joined us for somewhere around episode 34, where we talked about bring your own client. So, anyways, I thought it would be fun, especially because both of you work together on this research project to get you here together. So you can go back and listen to those episodes if you want the full backstory, but maybe you could each give a 32nd summary bio of yourself before we dive into the project itself. 00:04:51 - Speaker 3: Yeah, so I’m a grad student at MIT as well as a collaborator with the In and Switch Research lab, and my research mission is to figure out how to make software more customizable so people can edit the tools that they use and make their own software, and the project we’ll be talking about today has a lot of resonance with that theme, so excited to be here again. 00:05:12 - Speaker 1: And this is my first foray into research. I’m a software designer. I’ve worked on things like Hiroku, GitHub, cloud app, way in the past, and generally I like to summarize. My efforts as I like to make things for people who make where make is the developer build tool. 00:05:33 - Speaker 2: And our topic today will be dynamic documents, which indeed is what the potluck project that you both worked on and recently published about is all about. So we’re hoping to dive into the specifics of that project as well as some of the research process behind it. Maybe we could start out with a description, kind of the, I don’t know if elevator pitch is the right way to talk about a a research project, but a short summary. 00:05:58 - Speaker 3: We’re not raising funding, but I can give a summary, sure. So, Potluck is a substrate that we’ve been developing, where the goal is to turn regular old text documents into interactive tools that help you in your life. And so there’s this idea that you can just start by, you know, jotting a note on your phone like you might in an app like Apple Notes, and then gradually you start enriching that note with little bits of computation and interaction. And if you keep doing that for a while, you might end up with something that looks suspiciously like An app that you might download from the app store, but it’s not like someone else made it for you, it’s sort of organically evolved out of just a note that you started writing, and, you know, some examples of the kinds of things that we’ve thought about in the substrate are You’re writing down a recipe that your mom told you for how she makes her dumplings, and then you decide, oh, I’m gonna have a party, so I want to make 5x the recipe. What’s like 730 g times 5. That’s something that a computer should be able to help you with, right? But if your data is in a text note, how do you bring in the computer to play its role and help you out a little bit? We’ve developed these primitives where you can start injecting these little bits of computation as you need them into your text note. And so, that’s kind of the overall idea of the project. One analogy that I think is helpful to understand the general ethos of it is spreadsheets. I’m a huge, huge fan of spreadsheets. I think they’re a really empowering medium that people interact with pretty typically on a computer these days. And the cool thing about a spreadsheet, right, is that when it starts out, it’s just a bunch of numbers in a table. It’s just data sitting there, and it’s already useful in that state. And then gradually you might add a little formula, you might add a V lookup, and if you keep doing that, by the end, you might end up with this ridiculously complicated app that’s running your whole business, but it didn’t start out that way. It wasn’t planned to happen that way, it just started out as this little bit of data that you were storing, and it naturally evolved, right? So that’s kind of the general idea. 00:08:04 - Speaker 1: Yeah, there’s the well known meme of this insert startup could have been a spreadsheet, and I think in this case, you could probably make the same argument that this app could have been a note. And in fact, I would love to be able to do this at scale, but like if you just open the average users notes apps, what kind of notes do they take and, you know, throughout the course of this research project. That was sort of a grounding force of, oh, what kind of notes do people keep track of and so we started looking at, you know, like Jeffrey was saying recipes. At some point we did workout tracking and plant water tracking and like collecting your favorite hikes and so on, and they all have this sort of very innocuous beginning. You’re not planning to make something big, you’re just sort of planting a little seed as a note and What was frustrating for us is, at some point, if you then want a little bit more help from the computer, you usually have to move it out of the notes app, which is a little bit sad because it’s this big drop off, and so that’s kind of what we’ve been looking at, like, how do you make that go away. 00:09:14 - Speaker 2: And I love the diversity of use cases outlined in the essay. You focus on this cooking use case as a sort of a central one, even baked into the name of the project, but indeed all of these different kind of personal tracking stuff that tends to get scribbled down in notes and and in particular notes in your phone, text notes in your phone, that they’re not very structured, you’re trying to capture them in the moment and move on. And certainly many of those are things I have done, but also there is a whole industry is a way to put it, category of app which is trackers. So, yeah, hike trackers and run trackers and sleep trackers. And yeah, fitness trackers, step counters, weight trackers, you know, and sometimes that’s paired with, I don’t know why, you know, Fitbit has their Wi Fi connected scale, and when you step on it every morning, it automatically records the data, but then a weakness for someone who is both curious and has some light programming capabilities is actually getting that data out or doing something with it in a more flexible tool like a spreadsheet. is often pretty difficult. Actually, Fitbit, I think even famously had a little bit of pushback for the, you had to pay for the feature to kind of like download your data as a CSV and even then it feels like this very discontinuous, OK, I’m exporting now, the data, who knows what format it’s even in, and there certainly can’t be a continuous using of the app, inputting of the data, and then also I’m gonna put it through my own, call it personal analytics. 00:10:43 - Speaker 3: Yeah, and I think another weird thing about this ecosystem of trackers is that it sort of splits up your life into these very specific categories, right? So, for example, after my workout, what if I have a nutrition shake and I’m tracking my nutrition, I need to switch from my workout tracker to my nutrition tracker, and there’s this sort of world that each app considers its space that it doesn’t go outside of, you know? This also happens when, you know, We looked a lot at recipe apps because we were thinking about cooking as one of our main domains with this tool, and a lot of cooking apps start out very simple with tracking your recipes, but then there’s sort of a natural force to bloat them with extra stuff, so, You’ll add grocery list stuff, and you’ll add menu planning, and, you know, meal planning for the week, and all these. 00:11:29 - Speaker 2: All of your friends, what are they cooking? 00:11:31 - Speaker 3: Yeah, like social, you know, and I feel like we’ve all experienced this tool starts out nice and small and grows in weird ways. And what I think is important here is, I’m fine with it growing in the ways that I want it to be useful. What’s annoying to me is having 100 things crammed in there that I don’t need and can’t remove from the tool. And then on the flip side, the one extra thing that I do need, I can’t add myself, right? So, we sort of like, let the developer of each tracker decide what does cooking or what does workouts mean, like, what’s the scope of that activity, and it’s really hard to permeate that kind of boundary that gets set there, and so that’s one of the problems that we were thinking about in developing potluck. 00:12:12 - Speaker 2: So some of the key concepts here, dynamic documents is obviously a spreadsheet is a dynamic document, but the idea here is taking text, plain text, which is incredibly universal. Everybody’s phone has some kind of plain text notes app just kind of built in by default, but then you can use gradual enhancement to add some computation and make it something dynamic while keeping that same basic medium of just simple text you can manipulate. That you also talk a little bit of the essay about personal software, which I think is precisely this concept you’re just describing here, which is rather than my run tracker being an app that I download from the app store and I’m more or less just have to use it as intended by the developers, that I can use the computational medium to build a quote unquote application that just suits my needs, is truly personal. 00:13:05 - Speaker 1: Yeah, personal software is, well, first of all, I think it’s getting more mainstream in the sense that if you look at a lot of people’s notion, usage, and all the other insert, you know, personal knowledge management tool here where people are sort of aggregating all of this stuff in their life into a personal OS and I don’t know where the appetite comes from. I don’t know if it’s tied to increased computer literacy, at least some form of computer literacy, or it’s people have been burned by their favorite app changing either by adding too many features or just being deprecated, but there seems to be a lot of energy around it and so one of the things that is surprisingly Or rather, something that you wouldn’t think about right away is when you start building these apps from scratch from a note, you never really notice that you’re actually making a big complicated thing. You’re just starting out with some text and at some point you start adorning that text with some functionality and you just keep going and going and going, and at some point you wake up and you’re like, wait, this is actually quite complicated logic. Am I a programmer? And for us, that sort of was quite important, right, like embracing this notion of personal software that is truly yours, not from some team somewhere in Silicon Valley or wherever else deciding what’s best for you. And I think Jeffrey, you gave this analogy early on to like imagine our homes were Just furnished completely by other people, and all the objects in there just are sort of almost immutable, like we would not have that, and we do with software, and so I think nudging at that is super interesting. 00:14:53 - Speaker 3: This is one of my favorite ways to Open up my own mind to how weird software is, is to use analogies to other parts of the world, you know, I think we sort of have gotten so familiar with these metaphors of how software is organized. Like, in some sense, in this potluck work, what we’re doing is arguing against the idea of applications, right? Which is a really weird argument to make to a typical computer user, you know, it’s fish and water, like, what do you mean? I love apps. Apps are how we do things on computers, but It doesn’t have to be that way. I mean, Alan Kay, who’s responsible for a lo…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/68-multiplayer/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: The importance of solo activity in the ideation process. This is not well supported in existing tools. I think it’s so important that you have a place where you’re just thinking by yourself. That might be because you’re generating the initial ideas that you’re going to bring to the bigger group, or it could be you have some intermediate products from the group and you want to take that back to your private sanctuary and mark it up or sketch it or remix it. 00:00:31 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac. This podcast isn’t about Muse the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGrenigan. Hey, Adam. Mark a book I’ve been reading lately was suggested to me by our mutual colleague Julia is called Exhalation, which is a collection of short stories by Ted Chang, hope I’m pronouncing that right, who I think is best known for writing the book that Arrival was based on, but is a pretty prolific science fiction author in particular short story. Are you familiar with his work? 00:01:09 - Speaker 1: Yeah, well, I’ve seen Arrival, but I don’t think I’ve heard of his writing. 00:01:12 - Speaker 2: Yeah, I can highly recommend it, and I don’t think Yuli is even a huge sci-fi fan, so that’s why it stood out to me when she recommended it, but it’s really fascinating because I think each story, some of them are really short, just pose sort of a hypothetical universe or hypothetical setup. Where, what if the world was like this, and let’s just explore that philosophically. So one of my favorites in there, which I think also the collection was named after, is about a creature who is essentially what we would consider kind of a robot, but their whole circulatory system and neural system is based on the flow of air. And their whole energy source comes from pressure differentials within their universe, and physicists in their universe have discovered that basically there’s a fixed pressure differential from outside like I don’t know, a bronze sphere or something that contains the entire universe and it’s just kind of like a alternate reality. Posing of a, I’m not even sure way to put it, but it’s fun to read and explore the universe, but it also ends up posing questions about our own world, I think, in the way that only science fiction can. So, yeah, recommend it if you’re looking for something of that nature. 00:02:20 - Speaker 1: Ah, interesting, and that alternate physiology idea reminds me of, I think it’s called Hail Mary, Project Hail Mary, yeah, by Andy Weir, that’s a fun sci-fi book. 00:02:32 - Speaker 2: Hm, I wanna know this one. I’ll put it on my list. Well, there’s a fun little announcement here. The Muse team has started work on a multiplayer or call it a collaborative version of Muse. In the very early stages of that, but this is something you and I have talked about a bunch of times on the podcast, typically when questions of roadmap come up, right? I always think of the Muse master plan as kind of being the step 1 iPad app for thinking, private thinking, step 2, sync to your devices, your different devices, and then step 3 is being able to bring other people into the mix. And step 4 is end user programming, but we’ll save that topic for another day. That match with how you usually think about it. 00:03:14 - Speaker 1: Yeah, that’s the master plan. 00:03:16 - Speaker 2: And we wrote a little memo that we’ll talk about in some detail here today, but importantly it links to a survey, just a very short survey where we’re looking for some teams to help us out in, I would call it alpha testing, but really it’s about understanding how teams might work in a setting like this. So of course the Muse mission is to help individuals be more thoughtful through the tool. We’ve done that through our private thinking to date, but if we come into a team or group, I ideation setting where there’s any other person involved, now we kind of have to go back to our early principles and figure out how that fits in. And so one of the things we want to do is work really closely here with teams that have a particular shape. They’re a certain size, they’re working on certain kinds of problems. Problems to help us craft, not just kind of features or whatever on the product, but really understand the best workflows and the best way so we can help, in particular remote first team. So I’ll link to that survey as well as a memo on group ideation here. So naturally our topic today is multiplayer, or I think collaboration is what I historically had called it. Maybe in the local first paper we use the term real-time collaboration to refer to the kind of Google Docs era of you expect that there is a single location for a document that you’re working on with someone that’s sort of always up to date. Anyone who has the right permissions can make edit. It’s, I think multiplayer become the trendier word, so what exactly we’ll call it is still up for discussion. But anything in which you’re bringing in another human to your thinking process is just a whole new area for you and traditionally we’ve even been, I would call it a sanctuary for your private thinking. It’s almost like this notebook and The fact that it is just yours is part of maybe what makes it special. So, what does it mean to bring other humans into that process? What’s the first thing you think of on that front? 00:05:07 - Speaker 1: Yeah, well, we had joked about this long running master plan, but we’ve had such a consistent vision behind this because it reflects our long running understanding of how ideas are made. You know, recall the original impetus from you was, can we write software that helps people have better ideas? And in order to do that, the zero step is understanding where ideas come from. And yes, as you get new and better tools, it changes around the margins, right? But there’s very long running patterns and practices and how ideas are formed, even from before there were computers. And we’ve studied those a lot in the labs and at Muse. And one of those ideas, for example, was that you have these different form factors that you use for different parts of the creative process, the tablet, phone, and the desktop. Another important finding was that ideas don’t come from single people. They tend to be recombinations of existing ideas which overwhelmingly come from other people. And in fact, we’ve called the original versions of Muse a private sanctuary, but the first thing you do is you bring in inputs. That’s the first step of the creative process that we’ve talked about. And those inputs tend to come from other people. So, even in its early forms, Muse was embracing this idea of thinking and forming ideas as a multiplayer activity. It’s just that the person crossing boundary aligned with the Muse software boundary. Now we’re expanding the new software boundary. 00:06:28 - Speaker 2: Mm, right, so in this case, if I wanted to remix, recombine ideas, input from other people, let’s call it the outside world, I bring that into my private sanctuary, I bring in the tweets, I bring in the PDFs, I’ve got my excerpts, I’ve got my web clippings, I’ve got a copy paste or something, someone sent me in an email. I’m kind of putting all that together in one place on a board, so I can kind of see it together, start to connect the dots, start to see patterns across it. But once I’m inside the bubble, let’s say, of muse, then, you know, I know that that is mine. Nothing is put there by another person or even by an algorithm, right? Anything that’s on a board is cause you decided to put it there. That’s part of how we approached it. Yeah, and maybe that’s the input side, right, the snippets, the gathering, the reading notes, the inspiration from elsewhere, but there’s also an output side, which is at some point you do need to transmit these ideas to someone else. In many cases that is gonna mean you could do something like directly sharing a board screenshot or a PDF. A lot of people do the Choctaw style thing where they Share muse over a Zoom screen share or something of that sort and just kind of talk through it, or maybe like a loom, you know, folks who, they basically walk through their boards full of, say, like design crits or something like that, and then they share that kind of recorded video with their team, and you don’t need muse, but you’re using the muse boards as a visual to help transmit the ideas that you’ve come up with. But sometimes it’s going to a production tool from there. So for me that would often be something like just an email or a slack thread, or if a little more seriously you want to impress someone, a client, an investor or something, maybe you’ve got a slide deck. So I’ve got the rough shape of what I want to say in muse now I’m gonna copy paste pieces of it into an email or into that slide deck creation software and that kind of pseudo. Yeah, it’s partially copying, maybe partially it’s transcription, rewriting, but I’m taking this rush sketch of an idea and taking it into this other tool where I can make it into something that I guess is consumable by other humans. 00:08:32 - Speaker 1: Right. Yeah, and so when we talk about muse embracing multiplayer or collaborative capabilities, really what we mean is that middle stage, the stage of ideation, brainstorming, outlining, sketching, forming, reforming, that going from The single player activity that has been amused to date to involving multiple people. 00:08:55 - Speaker 2: And here I would be remiss if I didn’t reference a big influence on my thinking is Nicholas Cline, who we had on the podcast some time back. Of course I’ll link that episode in the show notes, but he has a whole sort of career spanning hypothesis, you might say about what he calls collaborative creativity, and there’s a very revealing diagram there which is that In many cases, the process for an individual thinking through something is you have an idea in your mind, but then you go to externalize it in some way. That could be just jotting down in your sketchbook or writing it into a text file or even explaining it to another person, and it is that process of getting it out that you kind of get new perspective on it and you’re able to refine, there’s a sort of a feedback loop on that. There’s also some famous quotes from Richard Feynman about his process of thinking through, you know, physics problems, where the notes on the page, he basically argues they’re not an artifact of his thinking, they are his thinking. The page is a sort of an extension of his brain in this case. And so, Nico’s concept of collaborative creativity, which obviously is very heavily informed by the work he’s done at FIGMA the last few years, is one of, OK, can we add another person into that mix in a way that’s productive versus disruptive, and yeah, again, we’ll link that in the show notes for those who are interested, but I think there’s a potentially an interesting parallel for the right kind of collaborative thinking. And I think this to me comes to an important distinction between the kind of relationship you have with a collaborator where you’re truly going to think together versus one that’s maybe more someone that you want to, let’s say, impress, I mentioned like clients or investors or applying for a grant. There you definitely want to externalize your thinking, but your goal is not to collaboratively think through. Something with the person on the other end, your goal is to transmit it to them or impress them or get them to buy your product or get them to invest in your company or whatever it is, whereas I think the collaborative creativity perspective and where I think we have more to say is one where you really have this true back and forth, and that includes What I would call creative trust. This is a term I’m borrowing from Hilary Maloney, who was on our podcast a little while back as well, but here, this brings you to being a team. And I think we talked about, well, too many Metamus references here, going back to the hiring episode, but the difference between me maybe pitching to a client and me bouncing ideas back and forth with someone that’s on the same team with me, that there’s a different quality in how we have creative trust in each other, and I think that Second one, that team or colleague, where we have this shared purpose and we’re working together, and we have this trust in each other, that can and I would argue, should create a setting where we should think things through together. 00:11:52 - Speaker 1: Yeah, exactly, and I think relatedly, there’s a difference between a production process versus an ideation process. To some extent this is kind of the other side of the coin you’re talking about, for example, with producing a deck for investors. There’s different output desiderata, there’s different constraints, and you come in hopefully with a relatively well-formed idea of what you’re actually trying to say. And we can elaborate more on this throughout the podcast, but it really is a different type of tool and kind versus a production tool for presentation and dissemination. 00:12:25 - Speaker 2: Yeah, that part of things is very parallel to how we think about the individual tool, which is, you know, part of the that we’re making with our company and part of the argument we’re sort of making to the world is that it is worth having a purpose-built tool for thinking and ideation and have that be separate from your production tool. So, one articulation of this might be, if you’re a writer. is the best thing to do to sit down at the typewriter in the kind of historic setting, or maybe nowadays the word processor, and you’re looking at that blinking cursor on an empty screen, and I would argue pretty strongly no. And we’ve even pointed to examples of purpose-built writing tools like Scrivener, where they actually have a separate product that is a companion product that is an open canvas for ideation and figuring out your story. I think they focus more on fiction writing, because they really recognize that you don’t want to do that in The writing tool because that’s a production tool, and if you’re figuring out the flow, your characters, and the flow of the story and the big arcs and that sort of thing, it’s just kind of the wrong level of detail in a way. And there’s a similar argument that could be made for, don’t just sit down at a blank code editor when you’re building a new piece of software, you know, get out there and whiteboard some of the basic architecture in what you’re building, or similarly with the design that you don’t necessarily want to start in a hyperfocused design tool where you can be hung up on corner radiuses and font sizes, you wanna be sketching it out in kind of very, very broad strokes. So, we’ve made that argument on a private basis, but there’s a team. Or kind of group version that’s very similar, which is, if you’re jumping into those tools of the trade, you’re gonna be pretty focused on production details when what you need to be figuring out is, big picture, why are we doing this? What are our values, what are the goals, what are the non-goals, what do we hope to accomplish, etc. 00:14:20 - Speaker 1: Yeah, now I’m wondering if we try to enumerate what these key differences are. An example of that would be if you and I were scientific collaborators and we were ideating, we would go to a blackboard and sketch some diagrams and some, you know, equations maybe and if things are going well, maybe you and I can read it. Whereas if we are publishing a scientific paper, we’re gonna go and type that in Latte, which is a whole ordeal, but it’s gonna be read by thousands of people, hopefully, so it’s worth that investment. And on the flip side, you already know what you want to say, so you do…

    Full show notes at the publisher

    https://museapp.com/podcast/transcripts/69-narrative/ Oct 05, 2023
    Show notes

    Discuss this episode in the Muse community Follow @MuseAppHQ on Twitter Show notes 00:00:00 - Speaker 1: You’re saying come dream with me a little, and if you get too much into the fantasy world, it becomes almost religious, and that’s where you get something like a WeWork happening. But when you can make the argument in a coherent way and are able to earn parts of that argument, then that come dream with me can be extremely compelling and can take outsiders along for the ride with you. 00:00:30 - Speaker 2: Hello and welcome to Meta Muse. Muse is a tool for deep work on iPad and Mac, but this podcast isn’t about Muse the product, it’s about the small team and the big ideas behind it. I’m Adam Wiggins here with my colleague Mark McGranaghan. Hey, Adam. And joined today by Mario Gabrieli of the Generalist. 00:00:49 - Speaker 1: Hey, great to be here. 00:00:51 - Speaker 2: And Mario, I understand that before your life in tech, you were working in a Michelin star restaurant. What was that like? 00:00:59 - Speaker 1: It was fascinating. I should clarify that I was truly the lowest man on the totem pole in the Michelin Star restaurant, so a lot of chopping vegetables and sort of assembling geometric and intricate salads and ceviches and things like that, but it was pretty fascinating to see what a high performance team in that environment looks like, and I don’t think it’s so different than a startup, you know, we had a very Strong sort of charismatic but efficient leader, a really well run team and like extremely high levels of motivation that, you know, I don’t know if I’ve seen even that many startups that have that level of drive from folks that were on their feet 1112, 16 hours a day, and obviously, you know, it’s not the most lucrative industry, so there’s a lot of passion and a lot of art in that that I respected a great deal. 00:01:53 - Speaker 2: I also feel like from what I’ve seen in the restaurant business, you know, chef’s table and other fictional representations that it’s almost has this performance element because of the timing and the real-time nature of it, you know, a startup, things may be fast paced, but ultimately, Maybe you, you know, ship once a day if you’re a very focused, continuous deployment type team, that’s something where you have, OK, it’s show time, you know, from 7 to 10 p.m. or whatever, dinner rush hour, all the food has to come out together and be the right temperature and so on. It feels like, yeah, there’s something almost theatrical to it. 00:02:30 - Speaker 1: Yes, 100%. It always felt very bad if I did a plate that chef was like, no this can’t go out. You’re like, oh gosh, I forget that we are judging it, you know, minute by minute here. Yeah, that’s an interesting thing to adapt to. 00:02:45 - Speaker 2: Now the Generalist is a publication, if that’s the right way to put it, I think so. 00:02:50 - Speaker 2: That covers business and technology. It’s something I’ve been reading basically since you got started, absolutely fascinating, very long form pieces that dive really deeply on a variety of topics, but often profiling specific companies, and I’ll reference some of my favorites there, but maybe you can tell us what the generalist is for you and yeah, the story that brought you there. 00:03:14 - Speaker 1: Amazing. Yeah, I think you did a great job describing it and have always very much appreciated you being a reader, so I’m grateful for that. The generalist is a what I hope modern media publication. We’ve started out with our deep dives, which are once a week we put out a deep piece of research usually about a company, as you mentioned, could be a crypto project, a venture fund or a trend. And the goal is to tell the story of that company in a way that both surfaces what makes it interesting and unique and the lessons behind it, but does so in a way that it really does feel like a narrative. And that’s both, you know, I think because of my own interests in storytelling and more sort of fictional styles of writing, but also pragmatic, you know, I think we all remember stories much, much better than we do. drier recitations of a subject and so the position of the generalist has always been If you really want to learn about these companies and the way that they’re impacting the future, the most efficient as well as the most enjoyable way is by packaging it in this sort of grander tale. And so the ultimate goal is, you know, build the most thoughtful publication in tech that has the depth of research of equity analysis, but a style that is closer to the New Yorker than a hedge fund. 00:04:42 - Speaker 2: I think when it comes to business analysis pieces, you might think of, for example, a high profile example would be stray, and you know, his analysis is excellent, but it is pretty dry stuff. You have to be really interested in the nuts and bolts and the inside baseball. Of technology companies and the industry and so forth, so yours strike me perhaps differently maybe that you spend time on the personal backgrounds of the founders and in many cases going back to who their parents were and what brought them to this place, but also telling the story in a context that’s I don’t know, it feels more like almost all of your briefings me feel like there’s something that could be adapted to like an HBO fictionalized, you know, TV show, not in like a sensationalist sense, but in the sense of a gripping narrative that you want to like follow through to the end, which is good because they’re also very, very long and detailed. 00:05:39 - Speaker 1: They are very long. Uh, thank you, that’s very kind. 00:05:42 - Speaker 2: To give some examples, we’ll link these in the show notes, but just some ones that struck me. One is the story of Telegram, which is a messaging app that basically almost everyone I know here in Europe uses it, especially after WhatsApp kind of went the Facebook terms of service route. And the backstory of that fellow and his time in Russia doing social media and then kind of his commitment to privacy because of that experience and just how huge it is. It’s like, hey, it’s a little messaging app all my friends use and it seems to be well executed, but the story there is pretty epic. Another example would be one called Andoril, and this is a defense contractor that uses software, and I think there is a natural, maybe knee jerk to anyone who’s making weapons of war or something adjacent to it, that that’s not a good use of computing or that there’s some moral questions there, but I think you do a good job of making an argument of why defense technology or war technology, which can be used for defense and offense is important. As well as just telling the story of this group that modernized it. And the third one I’ll mention is more of a blockchain kind of web 3 world company which is Helium, and this one’s also interesting, and maybe we’ll talk about your interest in the cryptocurrency and blockchain worlds, but it’s one that I’m probably a little more skeptical of and you seem to have more interest and enthusiasm for, but perhaps reading some of these deeper dives gives me more of a sense of like, OK, you know, there’s a lot of noise in this space, but there are some interesting call them success stories there. 00:07:16 - Speaker 1: Yeah, I think the helium one is a good example of how crypto can sort of divide people and you can look at the same set of facts and come up with, you know, very different conclusions. That one sparked a rather public debate on Twitter and amongst other media publications of, you know, whether helium is a success story or not, the usage is low, but the scale is broad, and so it’s always interesting to see. Which parts of the story matter to people? I think, you know, for better or worse, when I see something extremely novel, working at least in some really meaningful way, that to me is like extremely exciting, but you know, I think there’s also plenty of value in people saying yes, but here are all the things that aren’t working about it and, you know, the rooms for improvement. So that was a fun one and a stressful one. 00:08:09 - Speaker 2: And can you tell us a little about the journey that brought you from, at one point, working in a high intensity kitchen, and ended in creating this tech publication with these in-depth weekly briefings? 00:08:22 - Speaker 1: Yes, well, it might surprise you to hear that it wasn’t particularly linear. It was a lot of exploration and wandering from one place to another. I, despite my very American accent, grew up in London to an American mother and Italian father and sort of always spoken an American accent at home, just a lot of code switching, and came to the US for undergraduate, went to college and was very much of the mind that I was going to. Be a lawyer and then sort of move into the public sector. That was definitely my sort of mental model of how people made impact in the world and followed that, you know, rather assiduously through undergrad. All of my sort of internships were on the hill. I was extremely into mock trial and going every couple weekends to Iowa or California to compete in these, you know, literally sham trials, which was extremely nerdy and really had a pretty clear path there. But at some point I decided I wanted to study abroad and You know, like every good sort of truth seeking young undergraduate who has a passing interest in Buddhism, I went to Kathmandu and spent 6 months there, and it was extremely, extremely difficult, but also I think a valuable lesson in dealing with one’s own narratives about oneself. I know that’s sort of the topic of our conversation today, but You know, I think we are all predisposed to either inherit lessons that others have told us and take them as our own or develop them ourselves. And in the isolation of Kathmandu, you know, it’s very hard to get internet there. Time difference alone makes communication difficult. I think I started to recognize the cracks in my logic, although it would take a few years for me to. Sort of shake it all out. So, left undergraduate, got a job at a law firm that had a very interesting program in theory, which was, you know, you can do the work a 1 or 2nd year associate at a law school might be able to do. You can draft cross exams, you can write briefs. And so I got to work on some, again, theoretically interesting cases, one of the first Madoff cases, New York’s involvement with sort of reconstruction after Hurricane Sandy, but really quickly realized like, wow, my brain does not work in such a way as it is able to get enjoyment from this work. It is extremely like detail oriented and really much less about storytelling or writing or anything else. Or even, you know, if you want to get sort of righteous about it, justice or any of these other things, right? Like, once you see how the sausage actually gets made, you’re like, oh, we spent 9 months working on this case and then all of that was just to settle, you know, it was all a sort of game of chicken, like that is infuriating. And so I sort of realized, oh this is not gonna be the thing, and while trying to avoid doing as little work as possible at the law firm, I started to spend a lot of time on TechCrunch. And that was when I started to think like, oh, actually a lot of the interesting things happening in the world aren’t happening through government or nonprofits or anything else. They’re happening through tech. That’s where the impact is occurring, and that’s what is making a real difference. And so there were several other steps from there that, you know, I’m happy to go through, but that was sort of the moment that I started to become interested in this world. 00:11:49 - Speaker 3: And did you jump right to writing about it, or was there be steps between there? 00:11:56 - Speaker 1: Yeah, so I left the law firm. I had started at that point taking night school classes at NYU in fiction writing. Always loved writing growing up. I, you know, was writing a novel for most of my teen years in one way or another, you know, I’d sort of get like 100 pages in and then start on something different. And so that always really appealed to me. And so I thought, OK, I’m gonna take a year. I’ll apply to grad school because I need to be outwardly doing something. But really I will spend the year finishing a first draft of this novel I’ve started in night school classes. And take it from there. So I spent a year doing that, got into grad school, and after I had gotten into grad school and finished a draft of this book, I decided then to spend that summer going to culinary school and cooking at this Michelin star restaurant, which was a great like modern French place on 5th Avenue. Unfortunately it doesn’t exist anymore, but it was a ton of fun. And then again, sort of another few chapters of this exploration without a clear sight of what I was supposed to be doing. I did my masters in international development with a focus on tech and emerging markets. That to me felt sort of like a good interstitial, you know, intermediary phase between this international relations, politics, interest, and this sort of less certain thing about technology. So I did that. I worked in Bogota for 56 months, one summer working with like an incubator down there, getting to see these different startups. And then once I graduated, I really sort of more formally entered the world of tech for better or worse. So joined a startup called Eco, which was a fast platform for freelancers. We were acquired by Fiver after a couple of years and then joined a venture firm called Charge Ventures. Which was preceed and seed investing in New York. And it was while I was at charge that I basically had an old boss say, you’re an investor now, it probably would be useful for you to start writing about tech and sharing your thoughts online. And you know, ever since that NYU night school class, I developed this habit of getting up an hour or two before work to work on my novel at the coffee shop, you know, around the corner. And so I sort of was like, all right, like I think I know at least how to write a bit. Let’s see what this could become. And so, yeah, the generalist was born out of that little experiment and sort of quickly absorbed my interests and enthusiasm. 00:14:36 - Speaker 2: Timing wise, I feel like you went all in on this with a sort of paid subscription to your publication around the time that paid newsletters generally were starting to get popular, being in the zeitgeist, something like that. We talked with Dan Shipper from every, they started their business and were early on Substack. There’s obviously, yeah, Substack is a platform, but also other ways of kind of subscribing to individual writers or small groups of writers where you like their perspective and their take and you’re willing to just pay them directly versus the mediated stories that we get through, whether it’s something like social media feeds, Facebook. Reddit, Twitter, whatever, or even something like, you know, the classic kind of magazine you mentioned, the New Yorker, The Economist or something like that, that sort of bundles up, writing and reporting from many different sources, puts it all through a copy editing thing and then you purchase that bundle and this kind of direct relationship with a creator seemed like that’s pretty new in the last few years and maybe you. I don’t know what the order was there, whether you saw that that was kind of a growing opportunity and you wanted to be part of that, or if you just happened to start doing this around the same time, that was also an emerging trend. 00:15:49 - Speaker 1: Oh, absolutely, it was definitely luck. I had never read a sub stack before, but I remember seeing, I think, a friend of mine saying they were starting one, and I was like, oh, OK, for this new thing where I’m gonna write. Every week I’ll just try out this new tool since it seems like it’s inter…

    Full show notes at the publisher

    Previous 1 13 14 15 16 17 Next

    Related Podcasts

    Reply All

    1

    Reply All Games & Hobbies
    Inside VR & AR

    2

    Inside VR & AR Gadgets
    Note to Self

    3

    Note to Self News
    BrainStuff

    4

    BrainStuff Natural Sciences
    This Week in Tech (Audio)

    5

    This Week in Tech (Audio) News
    Hands-On Tech (Audio)

    6

    Hands-On Tech (Audio) Technology
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights