go through that high-level story and
think about what are the major
criticisms that would cause someone to
question your work to reject you to say
hey this stuff isn't good and then
figure out like come up with the
solution or your response to that and
tell it to people before they ask
all you needed to do for presentations
like make it video yourself doing the
presentation and then watch the video
right watch the video and imagine that
you know you're not you but you're the
person in the audience and show it to
someone else as well and see if it makes
sense to them right see if this whole
thing makes sense as you go through it
because a lot of times people will you
know will start teaching things and
doing things and they think it makes
sense and they go back and watch it and
they realize like man what the hell am I
talking about it made sense in my head
but now I'm looking at myself in the
video of me speaking and explaining it
and it really doesn't make it as much
sense anymore
or I included too many details right
that's a classic trap
trying to put all the details in the
presentation but the person you're
presenting to usually doesn't want all
the details and if they do they'll ask
so don't include every single detail in
the presentation you need to start by
creating a story right like you know
just use the star format what's the
situation
what's the task you're trying to solve
what actions did you take and what
results did you get all right start with
that overarching story and then start
filling in the information and then you
start thinking okay what else would
someone want to know like start
criticizing being critical of your
presentation and say where have I missed
something where did this project go
wrong and you basically want to figure
out all the objections of when someone
would actually tear apart your
presentation and you want to address
those before they ever have the chance
so you can say look you know we took
this approach we use the polynomial
regression because we saw this pattern
in the data and we believed that it
would give us a good fit however we
realized that this won't always work and
in the future we might need to use a
more complex algorithm may be something
decision tree based maybe a neural
network maybe something else but we
realized that's a limitation of the
project currently and we would
definitely update a more complex model
in the future if we had a data set that
required it so that way when people see
that you just did a root you know a
polynomial regression they don't think
that oh man this guy doesn't know
anything more complex you're
communicating hey
this actually this worked well today but
it could be a weakness if the data set
was more complicated higher dimensional
you know higher dimension data etc go
through that high level story and think
about what are the major criticisms that
would cause someone to question your
work to reject you to say hey this stuff
isn't good and then figure out like come
up with the solution or your response to
that and tell it to people before they
ask that's gonna show your awareness
that's going to show you thought ahead
etc and sometimes it's it's literally
just as simple as like hey I realize
that this system is not organized or
it's not automated or whatever because
we just didn't have enough time we only
have two days to work on this and if we
had more time here's how I would fix it
and improve it and do more so you can
add that on the end of like future
improvements what you do differently
what you would improve like that could
make up for anything almost just showing
that you've got the awareness to see
that there's still problems but you
already have solutions for them you just
need the time and resources to actually
implement the solution I always I always
wanted to try that basically going to a
hackathon and basically doing no work
literally doing no work and just coming
up with solution and telling people how
I would implement it what we would do to
solve the problem and just show them
nothing though and see if you win the
hackathon just based on the logic of the
solution and really explaining to people
and painting the picture and showing
them the vision of the future with
really no supporting work I think that
it would be more effective than most
people realize because in most
presentations people just focus on
technical stuff and they lose the big
picture and and you realize that
anything technical you do in present is
never going to be relevant for the other
person unless it's like an actual work
project for them so if it's like you
presenting during an interview or
something no one's really gonna care
because they're not gonna use your work
they're gonna hire you to do something
else
so painting the future vision is more
important than the technical work
sometimes even if you did work for them
they still want to see the high-level
impact and not necessarily the code that
you wrote so focus on the big picture if
they ask questions be ready to dive into
detail and like whiteboard it out or use
a flip chart or something
share the screen whatever be ready for
those be ready for the technical stuff
you don't necessarily have to include it
all in the main presentation
