Speaker 1: Today, I am back with Neo Applan, Inventium's Genai expert
Speaker 1: to help unpack a very cool concept that he recently
Speaker 1: shared with me. It's about gunslinging versus architecting, and it's
Speaker 1: all about how you work with AI. So if you
Speaker 1: have ever found yourself wrestling with chat, GPT or one
Speaker 1: of the other jenai is to get it just right,
Speaker 1: then this episode is for you. Welcome to How I Work,
Speaker 1: a show about habits, rituals, and strategies for optimizing your day.
Speaker 1: I'm your host, doctor Amantha Imber. Two years ago, I
Speaker 1: completely overhauled how I work with Genai and I'm now
Speaker 1: saving over forty hours every single week. That is no exaggeration,
Speaker 1: and that's exactly why my company, Inventium created the Genai
Speaker 1: Productivity Upgrade. It's a twelve week course designed to move
Speaker 1: you from AI doubler to productivity machine. No fluff, just
Speaker 1: practical strategies that will pay off from week one, saving
Speaker 1: you at least ten hours every single week. You'll learn
Speaker 1: how to make AI sound exactly like you use AI
Speaker 1: as your second brain to excel at your job, and
Speaker 1: so much more. Whether you're a complete beginner or already dabbling.
Speaker 1: We've got you covered, starting with prompting fundamentals and going
Speaker 1: all the way through to advanced automations and agentic AI.
Speaker 1: We kick off on July fourteen, and spots are limited.
Speaker 1: Visit inventium dot com, dot au, forward slash Jenai hyphen
Speaker 1: cohort to secure your place now, there's a link to
Speaker 1: that in the show notes, and you've got nothing to
Speaker 1: lose because there's a seven day money back guarantee, So
Speaker 1: head to the link in the show notes and check
Speaker 1: out the program today. So, Neo, you say that most
Speaker 1: people are gunslingers when they prompt Jenai, Can you tell
Speaker 1: me what you mean by that.
Speaker 2: Yeah, it's a metaphor. It's not a technical term. It's
Speaker 2: how some people work with jen Ai. It's effectively, get
Speaker 2: a decent enough prompt, shoot from the hip and hope
Speaker 2: and pray that it's going to go pretty well. Just
Speaker 2: as gun slinging isn't the most accurate way that you
Speaker 2: can hit a target, same thing with prompting gun slinging,
Speaker 2: where you've got a pretty average prompt, you've shot it
Speaker 2: out there, chances are it won't hit the bull's eye
Speaker 2: every time. And so what you're finding is you then
Speaker 2: have to have a discussion with the AI to improve
Speaker 2: the output. I mean a little bit more of this,
Speaker 2: a little less so that it can go from a
Speaker 2: discussion to feeling very much like a debate and argument
Speaker 2: with AI to get what you're really after. So the
Speaker 2: first prompt might be fast, but then the cleaning up
Speaker 2: is a very long task and can get frustrating after time,
Speaker 2: lots of back and forth refining, so it can be
Speaker 2: time consuming and inefficient if you're doing anything beyond kind
Speaker 2: of basic prompting or basic tasks.
Speaker 1: Okay, so then there is what you call architect What
Speaker 1: does that look like instead.
Speaker 2: Well, instead of shooting from the hip, it's much more deliberate,
Speaker 2: it's much more collaborative with the AI, and it's more
Speaker 2: likely to get you a great result and certainly faster
Speaker 2: than gunslinging. And that there's a lot less refinement and
Speaker 2: a lot less arguing with AI. So what you do is,
Speaker 2: first off, you need to agree with AI and what
Speaker 2: your goals are. Now, notice I say to agree, So
Speaker 2: you need to say, here's what my goals are, and
Speaker 2: you need to make sure that AI understands those goals.
Speaker 2: So here's what I'm trying to achieve. Then you also
Speaker 2: work with it on things like best practice or structure
Speaker 2: or all those kind of things before it starts writing
Speaker 2: anything else. So it's effectively you're working with it as
Speaker 2: a planning partner and getting it to challenge your ideas,
Speaker 2: getting it to challenge its own ideas, so it knows
Speaker 2: the structure, what you're trying to achieve, what best practice is,
Speaker 2: before you get it to write the thing. So it's
Speaker 2: almost like designing a house before you build it. You
Speaker 2: don't want to just build a house first. You want
Speaker 2: to design it first, and then when it's already designed,
Speaker 2: then you go and get the builders to come on
Speaker 2: and to build the thing.
Speaker 1: Okay, so I'm obviously not going to use architecting when
Speaker 1: I'm writing a simple email. So I'm wondering what are
Speaker 1: the kinds of tasks that architecting is best suited for.
Speaker 2: Anything it's complex or that you need to get a
Speaker 2: great result at where good enough isn't isn't enough, isn't
Speaker 2: good enough? You need to get something it's excellent. So
Speaker 2: things like if you're working on a strategy paper or
Speaker 2: training sessions or workshop design or any kind of report
Speaker 2: or analysis and all those kind of things, something where
Speaker 2: you need to make sure that it's grounding it in
Speaker 2: background and science and industry best practices and things like that,
Speaker 2: where you want to get a great result, This is
Speaker 2: where I would use architecting. So if you need a
Speaker 2: structured output or some thinking through it, it's really good
Speaker 2: for that. So if you wanted to have something which
Speaker 2: is average or it's quick, fine, gunsling, like if I'm
Speaker 2: doing emails off gunsling thing is fine. But if I
Speaker 2: want to get a document or a structure, or I
Speaker 2: want to, as I said, a team workshop. If I
Speaker 2: want a great team workshop, then why don't I get
Speaker 2: architecting to help me to build something even better. It
Speaker 2: works great with all the different ais, I should say,
Speaker 2: but in some of them it works better. So copilot
Speaker 2: architecting is brilliant. It does such a much better job
Speaker 2: than just average copilot gun slinging.
Speaker 1: And if I'm using chat ept, as I know a
Speaker 1: lot of listeners do, should I be choosing one of
Speaker 1: their logic models for this or any models? Fine?
Speaker 2: Yes, the logic models, and these are the ones that
Speaker 2: start in O so three to four, etc. The logic
Speaker 2: models are excellent for these kind of things. But they
Speaker 2: do a better job when you do architecting, because what
Speaker 2: you're still doing is you're working with the GENAI on
Speaker 2: what the goals are and things like best practice rather
Speaker 2: than letting it think. You're working with the GENAI to
Speaker 2: be able to architect this together, and those logic models
Speaker 2: do give you a better result. So yeah, do use
Speaker 2: the architecting, and those models you over next level the result.
Speaker 1: So NIO, I would love you to walk me through
Speaker 1: an example, like, let's just say I don't know you're
Speaker 1: designing a team building session for a client off site
Speaker 1: or maybe your own team's off site. How would you
Speaker 1: use architecting to go through that task?
Speaker 2: I would first start with the context, So here, I'm
Speaker 2: planning on building a team off site, and I'd like
Speaker 2: to build a structure with you. Tell it what your
Speaker 2: goals are. After that, I'd get it to ask itself
Speaker 2: what best practice is? Are there ways that I can
Speaker 2: achieve this goal even better? Get it to even review
Speaker 2: its own work to see whether it can improve it.
Speaker 2: What's the science behind team performance? All those kind of
Speaker 2: things to get it to think through all the best
Speaker 2: practice paths on how to build a great team workshop,
Speaker 2: I might work with it on say, structure, how would
Speaker 2: I structure these kind of things? What kind of activities
Speaker 2: would work. I'm not getting it to build the workshop
Speaker 2: or even the final output yet. I'm getting it to
Speaker 2: work through best practice, how it aligns with my goals?
Speaker 2: Are there better ways to do it? All those kind
Speaker 2: of things. Once I'm comfortable it's nailed what I'm trying
Speaker 2: to achieve, it understands best practice, it's refined as much
Speaker 2: as I think it needs to, then I'll go, Okay,
Speaker 2: let's build these things together. Then it will go through
Speaker 2: and actually build me a workshop, and it will say
Speaker 2: how and Wyatt's built the workshop for that best practice
Speaker 2: and how it will deliver to what I'm trying to
Speaker 2: achieve with those goals.
Speaker 1: And then I imagine you could break it down even
Speaker 1: further to go, okay, can we work on the morning
Speaker 1: segment first? And then let's work on the segment that
Speaker 1: is just before lunch and so on and so forth,
Speaker 1: as opposed to okay, build out the full agenda is
Speaker 1: Have I got my thinking right on that?
Speaker 2: Absolutely? Yeah? And this is really good for you. You've
Speaker 2: got a big document, say I'd be working on it
Speaker 2: with the goals the strategies what you need to do
Speaker 2: in the document, and then once you're comfortable with we'll
Speaker 2: call it like index or a table of contents, then
Speaker 2: you'd build out chapter by chapter, section by section, and
Speaker 2: that's much better to do it that way. That way
Speaker 2: it will give you a better result and it won't
Speaker 2: go off track at all. So yes, structure first and
Speaker 2: then section by section is the best way to architect
Speaker 2: and best way to get the results.
Speaker 1: Neo, thank you so much for coming on again. I
Speaker 1: know that we have recently in our own GENAI workshops
Speaker 1: been talking about these terms architecting and gunslinging, and I
Speaker 1: feel like there is that aha moment when people start
Speaker 1: to actually put this into action. So if this is
Speaker 1: resonated with you, I strongly recommend give architecting a go
Speaker 1: today when you are working with the AI to work
Speaker 1: on a complex task. If you like today's Joe, make
Speaker 1: sure you hit follow on your podcast app to be
Speaker 1: alerted when new episodes drop. How I Work was recorded
Speaker 1: on the traditional land of the Warrangery people, part of
Speaker 1: the Cooler Nation. A big thank you to Martin Nimber
Speaker 1: for doing this sound mix