Yeah. No worries. No worries. I was, about to call you, but you just appeared something like that. How are you doing?
Claudio Paolicelli
03:44
Good. Good. Thank you, Eugene.
Hai Ta
03:46
Doing great. It's it's sunny minus 20 here in Finland, Helsinki. This is my colleague, fun. She's a UX.
Claudio Paolicelli
03:56
Fine. Nice to meet you. Nice to meet you, Ron.
Hai Ta
04:00
Tagging along to, kind of hear the conversation and hear more about your thoughts. But yeah, how are how are things over there?
Claudio Paolicelli
04:10
Not too bad. It's not minus 20. It's minus like 5 or something. 1 is 3. It's not bad. I'm currently in, in, close to Manchester for, like, company meeting. Yeah, I mean, honestly, I like the product. I'm finding it really useful also because I'm just putting it in meetings where I'm not. So if it's for me.
Hai Ta
04:37
Let
Claudio Paolicelli
04:37
me do the notes, which is very useful. I got registration. I have to be honest I keep it away from confidential meetings and stuff because, you know, for safety reason, people don't like it to have it there. So it's fine. But for, like, routine stuff, stand ups, or, you know, meetings about project is is always there. Like, giving notes for me, which is very useful because my level of attention in meetings is very low.
Hai Ta
05:09
This this generation. Oh, now who are we heading? No. For sure. I understand. So you mentioned that, products stand up. I or daily stand up. I'm assuming this is like internal. And then project meetings may be also kind of internally aligned.
Claudio Paolicelli
05:24
It's all in time. I don't use the domain external
Hai Ta
05:29
Okay. Good. So can you, then kind of walk me through a bit how many of these meetings are having, every week. And what are the processes that happens after the meeting is over, once that you are in and once that you're not in. Like, I really wanna understand kind of the workflow in which Wudpecker is now a part of, of your daily.
Claudio Paolicelli
05:57
So, basically, I have I mean, he's basically in, all the stand ups, and I have 2 stand ups, the refinement. I'd say, like, 10 meeting a week at least which is the performance, the stand ups, and some meeting about, you know, last week. Okay. We have this problem how we fix it, stuff like that. Usually, what I do is I don't I don't always use it, actually. I don't always review the notes. I probably review the notes, like, later. Or if I miss something, I know that the meeting was important. So I use it, but I don't use it. In a sense, it's a safe, bake up, bake up for me. It's not something that I consult every every time in the minute, the meeting finishes, I go back there. But I know that the notes are there. So if I need something, I just can't go back there anytime and review it. That's why it's it's very comfortable for me. It's not just because I need to use it, but it's, it's get back up things for
Hai Ta
06:58
me. Mhmm. And how often then do you actually, review them on a weekly basis?
Claudio Paolicelli
07:05
Probably a couple of times top. Mhmm. The stand up, I'm not really interested in the stand up, unless there is a problem. And someone comes to me and say, Hey, we highlighted this problem in the stand up so I can just go review it because I'm working as a CTO interim. So I I don't really get into the day to day things, team. I use it mostly for the the bigger 1 when we need to do some refinement or we need to do some technology review, maybe to some system design. There there's loads of things that, loads of ideas thrown there. And I the way that the notes are taken is is very accurate. I like accuracy of the notes.
Hai Ta
07:49
So it's
Claudio Paolicelli
07:49
easy for me just to go there and say, okay, that's what we've decided. These are the action items it's quite accurate in that sense. So it's it's very useful for me. So it's not for the not for the day to day, but for the beaker planning meetings where those of things have been said on the same times for people just firing ideas and stuff. So it's everything that
Hai Ta
08:10
So they're kind of daily stand up. You how often does how often do you get ping about, hey, there's a problem, like, can you get can you take a look at it and then link the meetings or whatever?
Claudio Paolicelli
08:24
He's probably once every to once a sprint not more.
Hai Ta
08:29
Yeah. Good. Well, that's a good sign. The second part is that with those 10 can you can you describe a bit more? What what do you mean? What are the nature of these refinement meetings?
Claudio Paolicelli
08:41
It's, basically, something that we do for stand up to review the the job that we need to do in the in the spring. No, sorry, not for the stand up for the spring. So it's part of the spring planning. We get, all the job and the ticket that needs to be done. And we, and then we understand how are we gonna fit things in on the the team who's gonna work on stuff, basically. And, yeah, it's part of the planning. All these kind of index up that happens once every spring sprint that are, like, 1, 1 hour and a half meeting. So there's loads of things to be said because in the, in the stand up, it's quite it's quite quick. So there is nothing big, but when it's above long planning, long conversation, and I need the summary of the things, and it's a lot easier. Because sometimes in the stand up, I can just, like, hear the recording, I'm doing other things.
Hai Ta
09:31
Mhmm.
Claudio Paolicelli
09:32
Fine. But, for the long planning, I'm not gonna hear, like, 1 and a half hour to catch things. So that's when the notes really get useful for me.
Hai Ta
09:41
And so can just to understand the sprint, phase, so is it do you also do 2 week sprint? Yes. Yeah. So then there's like maybe 2 big meetings like once a week. So just planning and then the refinement.
Claudio Paolicelli
09:56
Not really because since we are a startup and we're really quick and we change things fast Okay. And is that after the planning, we might have another second planning because something changed or there is a clients that want something to be fixed. So we do another meeting than 1 hour. And that's when it really comes useful because I can review the notes of the previous 1 and understand what we've been said. I think what we've been planned again in the previous 1 and how this fits with the new 1. So I actually have 3 big meetings at least per week just to decide how last payment changes are gonna fit in the spring.
Hai Ta
10:32
Mhmm. Mhmm. Good. And then so let's say you have 1 of these important meetings and then what roughly at what point is it the about the time that you review the notes? And then what is done there? Do you then kind of add a kind of extract analysis and then put them in action items in Jira or whatever task management tool you use. Like, how does the note supplement you to the next thing that you need to do?
Claudio Paolicelli
11:03
So what I do usually is review the different topics. And understand where I have action items and I need to put them in my own board. For some important, I have a trouble with my own task. And then what needs to be communicated through email to someone, like, okay, we decided to talk to Thatnam and Thatnam has these things. So, okay, I'm gonna take the notes of that meeting, expand them in an email and send them to their clients, for example. So that depends on the conversation that most production items that it takes on. Those notes.
Hai Ta
11:37
So let's say, example, the email 1, how do you expand it?
Claudio Paolicelli
11:43
I usually, check the notes and just, like, write the email and, and do it, like, manually. Okay. These are the things that won't communicate. These are, like, you know, just doesn't drop. Like I said, that's my brainstorming, and then I just drop them in manually, basically. Or if I'm very lazy, I'm just ask charge if you need to do it. Mhmm.
Hai Ta
12:01
Okay. Yeah. So have you have you tried, ask Woodpecker for for this feature?
Claudio Paolicelli
12:07
I use it. I think once, just to ask something related to the meeting.
Hai Ta
12:12
Mhmm.
Claudio Paolicelli
12:12
Like, can you find me the point where these things has been discussed and you can get like something. Apart from that, nothing else, to be honest.
Hai Ta
12:25
Okay. Good. Because I was just thinking, is there any particular reason why, for example, you go to chat CPT instead of, using as Wudpecker
Claudio Paolicelli
12:34
I I just, like, didn't think it could have been used to to general, like, a generative AI, in the sense of drafting, like, email, like, in a chargeability sense. It was more like, something related to the meeting. Okay. Fine. Like, a search engine that's right. That way, it's it's just like how I see it, not because I didn't think it could have been done, basically. Yeah.
Hai Ta
12:58
That's good to know because then it's a onboarding issue for us because basically as what Wudpecker is built is using GPT 4 plus it already has all the transcript conversations. So in theory, it should perform better. Yeah. But it's good. Good to know.
Claudio Paolicelli
13:22
Read of the notifications came really loud.
Hai Ta
13:26
Yeah.
Claudio Paolicelli
13:29
Okay. Cool.
Hai Ta
13:32
Yeah. So I was saying that, ask what Panker would have it's it has GPT 4 plus it has a transcript conversation already in. So some context based in yeah, just just for future reference. Of course, you can.
Claudio Paolicelli
13:46
Yeah. Good to know. I can do everything in 1 platform.
Hai Ta
13:49
Yeah. Yeah. So that is my my poor messaging skills. So that's that's on on us. So no worries there. Really good to understand. Yeah. So I under so can okay. So you mentioned follow-up emails. So that's 1 thing that now I've discovered that you can also technically would be able to use Woodpecker for, had our onboarding been better Can you maybe give us a few more example of these action items that you typically do after those? Refinement or big meetings?
Claudio Paolicelli
14:28
Something that I do. Let me check some of the effects
Hai Ta
14:31
based for example, whatever you think that's like like generating email is quite a good example of what you can see.
Claudio Paolicelli
14:37
Yeah. Another things that I do usually is it's definitely like creating action items for for Jira, you know, like a ticket. I take the notes and I just, like, open and paste them in a ticket. Oh, okay. This is the things that we want to do. Or when we talk about in creating a new API, I just, like, clean the, just copy the the whole summary of what are the decision about the API. So what's gonna be the end point, all these things? Just Maybe it does something in Jira, but yeah. Yeah.
Hai Ta
15:12
Because another use case that, once we told similar users like youth is that, hey, Woodpecker will also be able to create, like, kind of text that changes the tone a bit so that it's as if it's a Jira ticket description. That kind of instructed, hey, you know, turn all the action items into, Jira take a description. So, again, another small use case may be, generative, could help you there. But if you already copy pasting stuff, then maybe not that much editing is needed anyways. Yeah.
Claudio Paolicelli
15:49
Yeah. Yeah, but if I could do that with, with the ask, feature, it would be easier because, yeah, it definitely would be, like, cleaner. Maybe using some DVD or version or something like that.
Hai Ta
16:02
Mhmm. Yeah. Good. Awesome. Is there any other, use you have been using Woodpecker for?
Claudio Paolicelli
16:13
Not really. I mean, usually, It's like most of the action items, emails, and maybe some, you know, some confluence I put things in conference. So I just, like, copy and paste that the notes as they are in a conference because usually when we have, like, big meeting, big decision, we put that in a technical form. So I put that and then I have some technical information in in the middle. Like, what's gonna be the URL and other things that from the movies are not, like, easy to catch, basically.
Hai Ta
16:44
Okay. So the the the conference documentation, is it, like, is it like a specific page for a client or just a new feature or some sort
Claudio Paolicelli
16:58
of is, as an is an internal page. So for example, if we discuss how we gonna design the architecture of the the new tax receiver, then I create, like, a new conference page, and I say, tax receiver for Slack, for example. And then I just copy and paste the old meetings, and that's that's the planning or are we gonna do the things? Some with Jackson, maybe, most of the the things are like because we talk in a very structured way. Okay? How we do these things. How are we gonna do this thing? So it's it's very easy for Woodpigot to put things in order. Okay. And the only things that I need to do is maybe add some some, you know, throw off the design c stamp or some sample code, some JSON Response, things that are not possible to physically discussing voice in the meeting.
Hai Ta
17:47
Okay. Perfect. Yeah. I think that's also very, very interesting. Good. And how often does that happen that you make a conference page?
Claudio Paolicelli
17:58
Probably That's 1 couple of times a week because we don't do many, like, organization and, and things like, you know, design system, things that need to document, heavily documented often. So, usually, it's, yeah, it happens, like, once or for as a month, not not more.
Hai Ta
18:17
Month or week. A month. Yeah. Yeah. Makes sense because you were saying a week. I'm like, wow, that's a HL company. No. Yeah. Good. No. Okay. This has been super insightful. I really appreciate your time, clarity on this. It's been great. Yeah. Now, I think basically the the the reason why we have these these interviews is, of course, wanting wanting to kind of validate our hypothesis of where we wanna go next. And I think some of the things you said, really hit home to where we wanna kind of bring the notes further. So for example, you have, let's say, this, these, calls in which you would create Jira, you could create Jira tickets out of them or draft the full of email. So if there are ways where we can detect that these are the things you care more about, then we would make it so that the notes generate those things. So you don't even necessarily need to ask Woodpecker for example. Now that's still an extra intermediate step. And I think, yeah, it's, it's, it's, there are ways we can kind of get there. And this is good to know that, okay, the way that we decide to solve this there's a need for or there's a problem there. So it's good.
Claudio Paolicelli
19:44
Cool. Thank you very much. After jumping at the core, but it was very useful. Thanks for, I I learned about the ask feature, which is very good for me as well.
Hai Ta
19:53
Yeah. Happy to hear. Happy to hear. Alright. Have a good rest of the day. Enjoy the minus 5.
Claudio Paolicelli
20:00
Thanks, April. Bye. Have a good day. Bye bye.
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
Claudio user interview