Welcome back.
So what we're going to do is we're going to start with project goals and I'm actually going to take
this little canvas here and I'm going to duplicate it.
I'm going to take this Koppio.
And what we can do is we can just make
our own you can barely see that, but we're going to bump that size right up.
So we'll pump it up to 80.
OK, perfect.
We were just going to make sure that that is like the.
So the reason why I have this set up the way I do.
Is because.
Well, everyone in the room to come in and bring their own thoughts to the table without having to raise
your hand, having to, you know, talk out loud about it.
Sometimes people are shy.
Sometimes there are more dominant voices in the room.
Give me one second.
What is the goal of the project?
Sometimes people just clam up, they don't really express what they truly believe is best for the project
sometimes, you know, generally if there's like a CEO in the room.
I find that's usually the case if there's like a boss and somebody I want to speak up.
So what I usually do is I give everyone stages.
So we're going to have to do here is granted that create a frame and this is going to be our sticky.
So like I said, you can do this in figure if you want.
Perfect.
That will be our sticky.
That's a pretty big sticky.
So what we're going to do here is we're just going to send her this.
And this frame is going to.
So, yeah, we can do this in Sigma.
I've done it in Sigma before, I thought it was really helpful.
We're just going to set our constraints so that when we resize this box.
Everything gets resized within, OK, so we can actually get rid of a lot of these colors.
And we can just rename this, OK, perfect, so what we're going to do is we're going to ask the main
question of a project of what is the project or what is the goal of the project.
And we're going to get everyone to write down on stickies what they believe is the goal of the project.
So basically using like that Google Sprint model of, you know, diverge, go off and do your own thing.
And then after post those stickies on the whiteboard or the digital whiteboard, whichever one you feel
comfortable with or whichever one you're forced to use in the moment, and then converge, come together
to kind of rank them, ask questions about them, see which goals there are.
There's usually multiple goals, whether that's user goals, whether that's business goals.
But we get a good understanding of what like the main project goal is here.
Now, let's get started.
Like I said, we want to figure out what a successful outcome looks like at the end of this project.
And like I said prior, it's done collaboratively, we really want to reveal everyone's perspectives
and then we can resolve any conflicting priorities.
Now, understanding specific activities the software will help people do should help provide a solid
foundation for making product decisions moving forward.
Some questions and answers are as follows.
What problems are you trying to solve for this project?
So some people may write something like we want to extend the key abilities of the application.
So maybe, maybe working on an existing application.
So you may want to have updates and that's perfectly fine.
That happens sometimes.
So that could be one another.
One could be.
We want to create an application.
To support a specific user task.
And generally, this is what we kind of see, rather see people wanting to build a new application or
extending the capabilities of an existing application.
Sometimes we want to build an application for something specific that a user needs to do.
I find that the best question to ask is something like what outcomes do you hope this application helps
you achieve during and maybe directly after this engagement?
So some answers may be something like make a sale to a customer.
Or sometimes a project will be more based on an MVP, like we need to present a proof
of products to potential investors.
Now, you may be thinking, oh, wow, these are way crazy goals like this.
Not something I would have thought about.
I was thinking maybe something like, I want to create an application to make sure people wake up if
it's an alarm.
But generally, sometimes there are other goals that we need to think about.
And this helps us really prioritize the type of work that we're going to be working on in order to showcase
certain things.
Like an example is with this sticky.
I often got this in my career.
I still do.
Sometimes we want to create like a minimum viable product MVP so that we can show that to investors
to show them why our product is viable and what is the quickest way to get there.
So what I usually do is I usually get all these different types of answers.
I get people to come together.
And they're going to rank these, you know, sometimes there will be overlap, sometimes another person
may say something like this create MVP, which is a minimum viable product, and these people will come
together and be like, oh, this is pretty similar.
So we'll just mop these together and we'll just call this one a proof of product.
And generally, if there are a lot of stickies that are similar, you'll know that that's a priority
for that team or that client.
And that's when you can really start ranking them.
But this is done collaboratively.
Now, what we really want to do is we want to get these people in the same room, like I mentioned,
working together, and you want the right people there that are going to really help define the success
of a project.
And over here, you'll be able to really pull out what the goals of the project are.
I'll give you one more example of what an answer could be.
One could be.
I want to attract
early users and show them that there is traction.
So if I think about this goal, I think about, OK, maybe an example of our product with habitual.
If we want to charge early users and show that there is traction, maybe we will focus on different
parts of the application, will say what are ways that we can do this?
An example being we want to show that users are signing up.
We want to show that users are selecting different types of categories or interests that pertain to
them.
And they're interacting with the application.
They're coming back.
The application is sticky, pardon the pun.
There are different ways that these goals can actually translate into things that you need to work on.
And that's it for project goals.