| Topic | Presenter | Summary | Duration |
| ----------- | --------- | -------------------------------------------------------------------------------------------------- | -------- |
| Note Taking | Clint T. | This video is from a Friday PM training where Clint T. covers the best strategies for note taking. | 58:00 |00:00:06.960 --> 00:00:09.228 This is me using the newer
00:00:09.228 --> 00:00:10.362 nicley no structures,
00:00:10.370 --> 00:00:11.458 so if you want to find this file,
00:00:11.460 --> 00:00:12.958 obviously you can type in the title,
00:00:12.960 --> 00:00:14.647 which I'll give you in a second.
00:00:14.650 --> 00:00:17.210 But you should be able to find it under PMO.
00:00:17.210 --> 00:00:18.146 The updated structure,
00:00:18.146 --> 00:00:19.706 which is still in progress.
00:00:19.710 --> 00:00:22.951 And then I specifically placed it under
00:00:22.951 --> 00:00:25.034 internal processes under internal
00:00:25.034 --> 00:00:27.580 policies how to take Meeting
00:00:27.580 --> 00:00:28.948 And I tried to structure this
00:00:28.948 --> 00:00:30.938 in a way that was easy to read.
00:00:30.938 --> 00:00:33.371 My goal here is to kind of get
00:00:33.371 --> 00:00:35.627 everybody on the same page or
00:00:35.627 --> 00:00:38.896 meeting
00:00:38.896 --> 00:00:42.268 the office and even early pandemic.
00:00:42.270 --> 00:00:43.426 Definitely something Kevin Kramer
00:00:43.426 --> 00:00:45.609 when he was leading a lot of these
00:00:45.610 --> 00:00:49.370 conversations was talking about because.
00:00:49.370 --> 00:00:52.490 We, as project managers also business
00:00:52.490 --> 00:00:55.678 analyst and broadly speaking as a company.
00:00:55.680 --> 00:00:57.840 If you're included in a meeting,
00:00:57.840 --> 00:01:00.008 most likely you're going to log your time.
00:01:00.010 --> 00:01:02.095 If you're not taking meeting
00:01:03.770 --> 00:01:05.690 I'm willing to bet you and I'm gonna
00:01:05.690 --> 00:01:07.470 use Kevin's exact ways of putting it.
00:01:07.470 --> 00:01:09.486 Willing to bet you you're not gonna know
00:01:09.486 --> 00:01:11.209 anything that happened in that meeting.
00:01:11.210 --> 00:01:12.617 You're just going to give me a
00:01:12.617 --> 00:01:13.753 rough summary and say, yeah,
00:01:13.753 --> 00:01:15.368 I think we discussed this.
00:01:15.370 --> 00:01:15.769 Yeah,
00:01:15.769 --> 00:01:18.163 I think we talked because you're
00:01:18.163 --> 00:01:20.787 listening but it's not active listening
00:01:20.787 --> 00:01:23.930 and that's the importance of meeting
00:01:23.930 --> 00:01:27.535 I have not done full scale audits
00:01:27.535 --> 00:01:30.699 like say Caroline or Kelsey have,
00:01:30.700 --> 00:01:33.412 but I certainly have looked into
00:01:33.412 --> 00:01:35.730 every project managers meeting
00:01:35.730 --> 00:01:36.645 And you know,
00:01:36.645 --> 00:01:38.780 I can personally tell you that I
00:01:38.851 --> 00:01:40.909 think we could do a lot better.
00:01:40.910 --> 00:01:42.926 I think a big part of it is that
00:01:42.926 --> 00:01:46.218 we don't have until potentially now
00:01:46.220 --> 00:01:49.256 some sort of template or structure
00:01:49.256 --> 00:01:51.582 in place and and that's really
00:01:51.582 --> 00:01:52.566 hurting us either.
00:01:52.570 --> 00:01:54.196 You're on calls and maybe you're
00:01:54.196 --> 00:01:55.832 not taking meeting
00:01:55.832 --> 00:01:57.087 you are taking meeting
00:01:57.090 --> 00:01:59.382 They become useless the day after
00:01:59.382 --> 00:02:00.910 because you've forgotten context.
00:02:00.910 --> 00:02:02.849 You didn't record what it is that
00:02:02.849 --> 00:02:04.429 was actually being talked about.
00:02:04.430 --> 00:02:06.195 Maybe only got the
00:02:06.195 --> 00:02:07.960 version and the Spark
00:02:08.018 --> 00:02:09.020 aren't very useful.
00:02:09.020 --> 00:02:11.840 And where this becomes especially
00:02:11.840 --> 00:02:15.290 bad is the wind devs need.
00:02:15.290 --> 00:02:15.944 These
00:02:15.944 --> 00:02:18.970 if they even get the chance to read them.
00:02:18.970 --> 00:02:21.273 They say things like and I've heard
00:02:21.273 --> 00:02:23.400 this straight up being told to me.
00:02:23.400 --> 00:02:23.700 Wow,
00:02:23.700 --> 00:02:25.930 I I don't know what I could
00:02:25.930 --> 00:02:27.755 possibly use those
00:02:27.760 --> 00:02:29.884 And so I'm being a little bit brutal here
00:02:29.884 --> 00:02:31.859 because I feel like this is something that,
00:02:31.860 --> 00:02:34.236 as as project managers in particular,
00:02:34.240 --> 00:02:35.488 but also business analysts
00:02:35.488 --> 00:02:36.736 are included in this.
00:02:36.740 --> 00:02:39.170 And arguably devs,
00:02:39.170 --> 00:02:41.018 this is a huge area that we need
00:02:41.018 --> 00:02:42.690 to improve on because I think it's
00:02:42.690 --> 00:02:44.760 leading to a lot of disorganization,
00:02:44.760 --> 00:02:47.497 a lot of forgetfulness, a lot of.
00:02:47.500 --> 00:02:50.020 Oh yeah, I remember us talking about this.
00:02:50.020 --> 00:02:52.834 I don't remember the exact details so.
00:02:52.840 --> 00:02:53.550 Broadly speaking,
00:02:53.550 --> 00:02:55.680 and I won't go through every
00:02:55.680 --> 00:02:56.920 specific thing on this.
00:02:56.920 --> 00:02:57.612 Broadly speaking,
00:02:57.612 --> 00:02:59.688 if you're included on a meeting,
00:02:59.690 --> 00:03:02.000 you have to take meeting
00:03:02.000 --> 00:03:03.956 That was what was established when
00:03:03.956 --> 00:03:05.917 I was joining the company and
00:03:05.917 --> 00:03:07.968 and was harped on quite a lot,
00:03:07.970 --> 00:03:11.380 and it has to be a policy and rule that
00:03:11.472 --> 00:03:14.530 we follow if we're not following it.
00:03:14.530 --> 00:03:16.490 Yadda yadda, I already mentioned
00:03:16.490 --> 00:03:17.834 failings that happened,
00:03:17.834 --> 00:03:20.522 so I listed a few requirements
00:03:20.530 --> 00:03:21.778 of what I think are important.
00:03:21.780 --> 00:03:23.698 So all team members present on the
00:03:23.698 --> 00:03:25.699 call should be taking active
00:03:25.700 --> 00:03:26.852 This is technically something
00:03:26.852 --> 00:03:29.010 even the dev team has to follow,
00:03:29.010 --> 00:03:30.956 but more often than not the dev
00:03:30.956 --> 00:03:32.370 team members included on a call.
00:03:32.370 --> 00:03:34.368 They're probably having to do something
00:03:34.368 --> 00:03:36.330 active which does make
00:03:36.330 --> 00:03:38.332 difficult and I'll get to that later.
00:03:38.340 --> 00:03:41.266 All team members must ensure that context.
00:03:41.270 --> 00:03:42.270 The meeting is understandable.
00:03:42.270 --> 00:03:44.030 You understand what I mean by that.
00:03:44.030 --> 00:03:45.938 When I show my examples below.
00:03:45.940 --> 00:03:47.920 But again, exceptions may include
00:03:47.920 --> 00:03:49.504 management or senior devs,
00:03:49.510 --> 00:03:50.675 I'm guaranteeing you if you
00:03:50.675 --> 00:03:52.210 have a Eric Weathers on a call,
00:03:52.210 --> 00:03:54.149 he's probably doing two things at once.
00:03:54.150 --> 00:03:55.922 If you have Brandon Murphy on a call, he's.
00:03:55.922 --> 00:03:58.154 Probably doing two things at once.
00:03:58.160 --> 00:03:59.770 There's going to be exceptions
00:03:59.770 --> 00:04:01.058 as a project manager,
00:04:01.060 --> 00:04:03.705 we cannot be that exception if you're on
00:04:03.705 --> 00:04:05.820 a call and you're important to the call,
00:04:05.820 --> 00:04:08.004 meaning you're the PM of the project
00:04:08.004 --> 00:04:09.826 or it's whether it's discovery
00:04:09.826 --> 00:04:11.466 or project status meeting,
00:04:11.470 --> 00:04:13.150 or even just an internal meeting,
00:04:13.150 --> 00:04:16.526 you should be taking some form of nodes.
00:04:16.530 --> 00:04:19.650 Lastly, all
00:04:19.650 --> 00:04:21.178 This is kind of two in the same.
00:04:21.180 --> 00:04:23.196 All
00:04:23.196 --> 00:04:25.160 template and all
00:04:25.160 --> 00:04:26.890 uploaded into the teams channel.
00:04:26.890 --> 00:04:29.128 Again, we can get into exceptions,
00:04:29.130 --> 00:04:32.651 but ultimately we need to be following
00:04:32.651 --> 00:04:34.650 these policies as much as we can,
00:04:34.650 --> 00:04:36.570 so I've included in here what
00:04:36.570 --> 00:04:38.640 I use as my template.
00:04:38.640 --> 00:04:40.224 And unless somebody magically
00:04:40.224 --> 00:04:42.600 comes up with a better template,
00:04:42.600 --> 00:04:43.448 this is the template.
00:04:43.448 --> 00:04:44.720 I think everybody should be using.
00:04:44.720 --> 00:04:46.817 This is the template I was provided by Kevin.
00:04:46.820 --> 00:04:49.067 This is the template I've always known,
00:04:49.070 --> 00:04:50.480 but maybe this isn't a template
00:04:50.480 --> 00:04:51.420 you've been familiar with,
00:04:51.420 --> 00:04:53.534 so I just downloaded this one here.
00:04:53.540 --> 00:04:55.700 It has the agenda meeting
00:04:55.700 --> 00:04:56.780 and if applicable,
00:04:56.780 --> 00:04:58.760 which I think it should be
00:04:58.760 --> 00:05:00.360 the action items you include.
00:05:00.360 --> 00:05:01.680 The clients name.
00:05:01.680 --> 00:05:03.000 Obviously the client,
00:05:03.000 --> 00:05:05.464 as in the company you're working with.
00:05:05.470 --> 00:05:08.640 I usually include something like.
00:05:08.640 --> 00:05:11.286 Let me enable editing a client
00:05:11.286 --> 00:05:13.050 name project status meeting.
00:05:13.050 --> 00:05:14.052 If it's discovery,
00:05:14.052 --> 00:05:15.388 I'll change this discovery,
00:05:15.390 --> 00:05:18.015 yadda yadda, UM, and then of course,
00:05:18.020 --> 00:05:19.886 the date if it's not the
00:05:19.886 --> 00:05:20.819 project status meeting,
00:05:20.820 --> 00:05:22.240 I would recommend changing this
00:05:22.240 --> 00:05:23.660 to say it's something else.
00:05:23.660 --> 00:05:25.940 Maybe it's a meeting with Syspro,
00:05:25.940 --> 00:05:27.608 maybe it's a meeting with this
00:05:27.608 --> 00:05:28.442 vendor or whatever.
00:05:28.450 --> 00:05:30.322 The more context you can give
00:05:30.322 --> 00:05:31.820 to what this meeting is,
00:05:31.820 --> 00:05:32.777 the more important.
00:05:32.777 --> 00:05:34.691 So I have the template there
00:05:34.691 --> 00:05:36.377 which you guys can download.
00:05:36.380 --> 00:05:37.745 I personally and this is
00:05:37.745 --> 00:05:38.837 just a best practice.
00:05:38.840 --> 00:05:41.306 I would highly recommend keep a
00:05:41.306 --> 00:05:43.619 folder structure where a lot of
00:05:43.619 --> 00:05:45.971 this is already set up in the CBI
00:05:46.045 --> 00:05:49.060 Connect channel under project management.
00:05:49.060 --> 00:05:51.380 I have standardized file structure.
00:05:51.380 --> 00:05:54.108 I copy and paste this into all my
00:05:54.108 --> 00:05:55.500 projects and what do you know?
00:05:55.500 --> 00:05:59.412 It comes with a generic project
00:05:59.412 --> 00:06:02.020 status meeting
00:06:02.020 --> 00:06:04.747 Again, a lot of what I'm doing might seem
00:06:04.747 --> 00:06:07.498 like additional work and additional time.
00:06:07.500 --> 00:06:09.698 But if you make your life easier,
00:06:09.700 --> 00:06:11.848 it takes me an extra minute,
00:06:11.850 --> 00:06:14.650 maybe at most so.
00:06:14.650 --> 00:06:16.426 Does everything I said makes sense?
00:06:16.430 --> 00:06:18.558 'cause I'm gonna kind of breeze through
00:06:18.558 --> 00:06:20.450 the processes as quickly as I can,
00:06:20.450 --> 00:06:22.214 but I want to make sure that
00:06:22.214 --> 00:06:24.069 everybody is kind of following along.
00:06:24.070 --> 00:06:27.614 Yeah, yeah yeah yeah no, it definitely does.
00:06:27.614 --> 00:06:30.094 Perfect. Uhm, no process.
00:06:30.094 --> 00:06:33.166 So I have this listed out
00:06:33.166 --> 00:06:35.862 into a number of agenda items.
00:06:35.862 --> 00:06:37.619 So how to prep for a meeting?
00:06:37.620 --> 00:06:40.525 Which means basically, what is your agenda?
00:06:40.530 --> 00:06:42.798 Where to take
00:06:42.800 --> 00:06:43.892 How to format
00:06:43.892 --> 00:06:45.530 where to save the meeting
00:06:45.590 --> 00:06:47.284 and how to follow up on meeting
00:06:49.000 --> 00:06:50.170 I'll go over an example.
00:06:52.190 --> 00:06:53.345 So how to prep for a call?
00:06:53.350 --> 00:06:55.198 This is pretty important and probably
00:06:55.198 --> 00:06:57.360 one of the most painful things.
00:06:57.360 --> 00:06:58.998 If your project status or sorry.
00:06:59.000 --> 00:07:00.750 You're a pro project manager,
00:07:00.750 --> 00:07:02.285 and you're going into a
00:07:02.285 --> 00:07:03.206 project status meeting.
00:07:03.210 --> 00:07:04.535 You've probably had those moments
00:07:04.535 --> 00:07:06.130 where 5 minutes before the call.
00:07:06.130 --> 00:07:06.994 You're like shoot.
00:07:06.994 --> 00:07:09.420 What are we going to talk about today?
00:07:09.420 --> 00:07:10.848 And so you kind of go into
00:07:10.848 --> 00:07:12.139 the call and you wing it.
00:07:12.140 --> 00:07:13.772 And maybe it's fine because everything
00:07:13.772 --> 00:07:15.803 is good and the developer who may or
00:07:15.803 --> 00:07:17.640 may not be on the calls like Yep,
00:07:17.640 --> 00:07:19.392 I did all this this and
00:07:19.392 --> 00:07:21.059 this and it's all on .0.
00:07:21.060 --> 00:07:21.500 That's great,
00:07:21.500 --> 00:07:23.488 but I'm willing to bet you you're going to
00:07:23.488 --> 00:07:25.162 get into a call where that's not the case.
00:07:25.170 --> 00:07:26.410 You don't have an agenda,
00:07:26.410 --> 00:07:27.780 the client asks you questions
00:07:27.780 --> 00:07:29.150 you don't have answers for,
00:07:29.150 --> 00:07:31.850 and then suddenly the clients
00:07:31.850 --> 00:07:33.578 asking what are we paying you guys?
00:07:33.580 --> 00:07:34.120 4.
00:07:34.120 --> 00:07:37.900 And it's a very very understandable question,
00:07:37.900 --> 00:07:40.350 because from their perspective and
00:07:40.350 --> 00:07:42.310 ultimately from management perspective,
00:07:42.310 --> 00:07:44.956 you have to know what this meeting is for.
00:07:44.960 --> 00:07:47.342 So my recommendation is ahead of
00:07:47.342 --> 00:07:49.809 the project status meeting and I
00:07:49.809 --> 00:07:51.829 would include the discovery meeting.
00:07:51.830 --> 00:07:53.030 Prep ahead of time,
00:07:53.030 --> 00:07:54.830 and ideally that's a day before,
00:07:54.830 --> 00:07:56.468 which is always why I say,
00:07:56.470 --> 00:07:57.870 you know, don't have meetings
00:07:57.870 --> 00:07:59.270 on Monday or external meetings.
00:07:59.270 --> 00:07:59.902 That is,
00:07:59.902 --> 00:08:01.482 give yourself some time on
00:08:01.482 --> 00:08:03.129 Monday to prep for calls.
00:08:03.130 --> 00:08:04.290 Give yourself some time
00:08:04.290 --> 00:08:06.030 to go through and say OK,
00:08:06.030 --> 00:08:08.478 what's what's our plan for each one of
00:08:08.478 --> 00:08:10.989 these calls that includes discovery calls?
00:08:10.990 --> 00:08:13.405 I'm guaranteeing you Kyle and Brian Lee.
00:08:13.410 --> 00:08:15.258 They were probably going to call
00:08:15.258 --> 00:08:16.793 right before the likelihood that
00:08:16.793 --> 00:08:18.245 they're going to be able to,
00:08:18.250 --> 00:08:19.942 you know, have an agenda for
00:08:19.942 --> 00:08:21.070 every single discovery meeting.
00:08:21.070 --> 00:08:22.876 Just because you set up the meeting.
00:08:22.880 --> 00:08:24.296 Is low, you know.
00:08:24.296 --> 00:08:25.358 Prep with them,
00:08:25.360 --> 00:08:27.064 chat him up and sometimes it's
00:08:27.064 --> 00:08:29.428 fine to do it 15 minutes before,
00:08:29.430 --> 00:08:31.500 but it's ideal to do it the day the
00:08:31.500 --> 00:08:34.480 day before, or even a week ahead.
00:08:34.480 --> 00:08:37.680 Give yourself that preparation and
00:08:37.680 --> 00:08:39.453 I've got some
00:08:39.460 --> 00:08:39.813 but.
00:08:39.813 --> 00:08:40.166 Uh,
00:08:40.166 --> 00:08:41.931 essentially you want to review
00:08:41.931 --> 00:08:43.481 the previous project status
00:08:43.481 --> 00:08:45.177 meeting or Discovery meeting.
00:08:45.180 --> 00:08:46.022 If applicable,
00:08:46.022 --> 00:08:48.548 review Basecamp and kind of review
00:08:48.548 --> 00:08:51.460 where the project is on a broad scale.
00:08:51.460 --> 00:08:53.542 If you're using and you should
00:08:53.542 --> 00:08:55.377 be the timeline Gantt charts
00:08:55.377 --> 00:08:57.267 for either connect or Seth.
00:08:57.270 --> 00:09:01.370 Those are hugely beneficial for.
00:09:01.370 --> 00:09:03.248 Seeing where your project is at,
00:09:03.250 --> 00:09:04.252 obviously it's important
00:09:04.252 --> 00:09:05.588 that you're updating them,
00:09:05.590 --> 00:09:07.950 but that can be kind of like an
00:09:07.950 --> 00:09:10.148 active
00:09:10.150 --> 00:09:13.590 Hey, a project timeline and you're seeing OK,
00:09:13.590 --> 00:09:15.310 everything in Discovery is completed,
00:09:15.310 --> 00:09:17.326 but we're still working on some environments.
00:09:17.330 --> 00:09:18.786 What do I need to bring up there?
00:09:18.790 --> 00:09:20.090 Do we need credentials?
00:09:20.090 --> 00:09:22.539 Do we need you know XY and Z?
00:09:22.540 --> 00:09:24.418 If you come to the meeting
00:09:24.418 --> 00:09:25.357 prepared with that?
00:09:25.360 --> 00:09:26.984 The client is going to appreciate it.
00:09:26.990 --> 00:09:28.922 The clients going to see value in
00:09:28.922 --> 00:09:30.926 what you're bringing to the table and
00:09:30.926 --> 00:09:32.612 ultimately the projects more likely to
00:09:32.664 --> 00:09:33.378 stay on track.
00:09:33.380 --> 00:09:35.396 So how can you provide an agenda?
00:09:35.400 --> 00:09:37.128 Well, for one internally it's helpful
00:09:37.128 --> 00:09:39.406 to just send a chat to any internal
00:09:39.406 --> 00:09:41.340 team members who are on the call.
00:09:41.340 --> 00:09:44.000 If you know, let's say,
00:09:44.000 --> 00:09:45.662 a certain team member is optional
00:09:45.662 --> 00:09:47.320 on the call, you can let them know.
00:09:47.320 --> 00:09:49.496 Hey, we will need you on this call
00:09:49.496 --> 00:09:52.217 or we will not need you on this call.
00:09:52.220 --> 00:09:53.894 Similarly, it can be very useful
00:09:53.894 --> 00:09:55.490 to just print people and say.
00:09:55.490 --> 00:09:56.282 And I you know,
00:09:56.282 --> 00:09:57.792 I sometimes only do this 15 minutes
00:09:57.792 --> 00:09:59.689 before where I just let everybody know.
00:09:59.690 --> 00:10:01.167 Hey guys I'm gonna go through the
00:10:01.167 --> 00:10:02.670 timeline then I'm going to go through,
00:10:02.670 --> 00:10:05.439 uh, action items.
00:10:05.440 --> 00:10:07.280 And then if there's any questions after that,
00:10:07.280 --> 00:10:08.640 we can go over that.
00:10:08.640 --> 00:10:10.340 That's a pretty standard agenda.
00:10:10.340 --> 00:10:11.570 It's nothing crazy.
00:10:11.570 --> 00:10:12.800 It's nothing insane,
00:10:12.800 --> 00:10:14.516 but it's good to let the
00:10:14.516 --> 00:10:15.660 internal team members know.
00:10:15.660 --> 00:10:19.790 The second thing is letting the UM
00:10:19.790 --> 00:10:21.158 client team know ahead of time,
00:10:21.160 --> 00:10:22.910 so there's.
00:10:22.910 --> 00:10:24.428 Multiple ways you can do this,
00:10:24.430 --> 00:10:26.626 and admittedly this is the aspect
00:10:26.626 --> 00:10:29.029 of agendas that I suffer with.
00:10:29.030 --> 00:10:32.078 I am not great about sending meeting
00:10:33.930 --> 00:10:38.400 Usually I in my meeting.
00:10:38.400 --> 00:10:41.208 Under invite I'll include the agenda
00:10:41.208 --> 00:10:44.348 within the actual body of the meeting,
00:10:44.350 --> 00:10:46.213 but an alternative that I put in here is.
00:10:46.220 --> 00:10:48.194 You can actually put the agenda section,
00:10:48.200 --> 00:10:50.248 which again pulling up this this
00:10:50.248 --> 00:10:52.872 agenda here I'll put the agenda in this
00:10:52.872 --> 00:10:55.220 section and delineate it by line items.
00:10:55.220 --> 00:10:57.676 So if we're going over the product sync,
00:10:57.680 --> 00:11:00.288 what's the action items from the last call?
00:11:00.290 --> 00:11:01.300 If you have those great,
00:11:01.300 --> 00:11:02.554 you can just copy and paste
00:11:02.554 --> 00:11:03.650 it from your previous call.
00:11:03.650 --> 00:11:04.840 If you don't have them,
00:11:04.840 --> 00:11:06.534 you'll definitely have to write them out,
00:11:06.540 --> 00:11:08.476 but it can be useful for your perspectives.
00:11:08.480 --> 00:11:10.504 So that you can pull up that agenda
00:11:10.504 --> 00:11:11.955 mid meeting and know exactly
00:11:11.955 --> 00:11:13.719 what you're going to talk about.
00:11:13.720 --> 00:11:16.856 If you do not know what to cover,
00:11:16.860 --> 00:11:18.162 This is why it's important to
00:11:18.162 --> 00:11:19.440 do it the day before.
00:11:19.440 --> 00:11:21.883 You can obviously reach out to different
00:11:21.883 --> 00:11:23.694 team members internally and and kind
00:11:23.694 --> 00:11:25.560 of get a grasp of what's going on.
00:11:25.560 --> 00:11:27.270 What's the health of the project?
00:11:27.270 --> 00:11:30.156 It is also possible it's beneficial
00:11:30.156 --> 00:11:31.599 to cancel meetings.
00:11:31.600 --> 00:11:34.426 I have all my meetings, meetings weekly.
00:11:34.426 --> 00:11:37.807 There are times where I don't have.
00:11:37.810 --> 00:11:39.586 A status update for the client.
00:11:39.590 --> 00:11:40.796 Nothing's really changed,
00:11:40.796 --> 00:11:43.208 we're just waiting on new things.
00:11:43.210 --> 00:11:44.708 Ideally you are not doing that the
00:11:44.708 --> 00:11:46.427 day of your not letting them know.
00:11:46.430 --> 00:11:46.786 Hey,
00:11:46.786 --> 00:11:48.566 I'm gonna cancel this call
00:11:48.570 --> 00:11:50.842 because obviously that's rude.
00:11:50.842 --> 00:11:51.978 But secondly,
00:11:51.980 --> 00:11:55.058 it can just lead to the client feeling like.
00:11:55.060 --> 00:11:55.406 Well,
00:11:55.406 --> 00:11:57.828 this is just being haphazardly put together.
00:11:57.830 --> 00:11:59.022 And to be fair,
00:11:59.022 --> 00:12:01.913 if you are cancelling the day of and it's
00:12:01.913 --> 00:12:04.321 not for a reason like somebody sickness.
00:12:04.330 --> 00:12:05.296 They're probably right.
00:12:05.296 --> 00:12:08.040 It is probably you being last minute like oh,
00:12:08.040 --> 00:12:08.272 shoot,
00:12:08.272 --> 00:12:09.896 I don't know what to talk about.
00:12:09.900 --> 00:12:12.460 I'll just cancel it so it's a good
00:12:12.460 --> 00:12:15.399 idea to reach out to Daniel or Kevin.
00:12:15.400 --> 00:12:16.672 Whoever is potentially overseeing
00:12:16.672 --> 00:12:18.878 that project and get a health check
00:12:18.878 --> 00:12:20.780 with them and say, hey, you know,
00:12:20.780 --> 00:12:22.950 I don't think this next meeting coming
00:12:23.016 --> 00:12:25.358 up will be a useful portion of our time.
00:12:25.358 --> 00:12:27.580 So let's go ahead and cancel that.
00:12:27.580 --> 00:12:28.819 That's totally reasonable.
00:12:28.819 --> 00:12:31.924 Please just do not do it the day of
00:12:31.924 --> 00:12:33.380 the meeting if you can avoid it.
00:12:33.380 --> 00:12:34.610 There are exceptions.
00:12:34.610 --> 00:12:36.660 But try to avoid that.
00:12:36.660 --> 00:12:40.860 So any questions there?
00:12:40.860 --> 00:12:43.300 No worries, if not cool.
00:12:43.300 --> 00:12:44.860 Where did take meeting
00:12:44.860 --> 00:12:49.767 I personally and very pro using meeting
00:12:49.767 --> 00:12:53.641 883e22ba-0961-47be-b8d9-b1f2a6c9c45c
00:12:53.641 --> 00:12:56.280 more exact on what I mean by that.
00:12:56.280 --> 00:12:59.540 A lot of the.
00:12:59.540 --> 00:13:00.458 Meetings we have.
00:13:00.458 --> 00:13:02.600 We set them up as reoccuring and
00:13:02.669 --> 00:13:04.469 the benefit of a re occurring
00:13:04.469 --> 00:13:06.385 meeting is that you can easily
00:13:06.385 --> 00:13:09.175 keep track of
00:13:09.180 --> 00:13:11.612 So what I mean by that is under
00:13:11.612 --> 00:13:13.380 the actual meeting itself.
00:13:13.380 --> 00:13:14.715 If it's reoccuring you can
00:13:14.715 --> 00:13:16.372 actually go over to this section
00:13:16.372 --> 00:13:17.974 called meeting
00:13:17.974 --> 00:13:19.717 do this on the call as well.
00:13:19.720 --> 00:13:22.296 So for instance right here I can
00:13:22.296 --> 00:13:24.871 come over and click a option
00:13:24.871 --> 00:13:27.643 available to me called meeting
00:13:27.650 --> 00:13:28.758 This does notify everybody
00:13:28.758 --> 00:13:29.589 that you're creating.
00:13:29.590 --> 00:13:31.888 Meeting
00:13:31.888 --> 00:13:35.392 And then this will open up the teams.
00:13:35.400 --> 00:13:37.914 A section here or it's like
00:13:37.914 --> 00:13:40.000 weekly PM training break out.
00:13:40.000 --> 00:13:42.415 I always type in
00:13:42.415 --> 00:13:44.539 I generally type in the actual.
00:13:44.540 --> 00:13:47.044 Date up just to help myself keep track
00:13:47.044 --> 00:13:49.379 of when I made made these
00:13:49.380 --> 00:13:49.720 Uh,
00:13:49.720 --> 00:13:52.100 so that can be hugely beneficial to
00:13:52.100 --> 00:13:54.419 take
00:13:54.420 --> 00:13:56.620 You can have this to one side so
00:13:56.620 --> 00:13:58.917 that you have everybody over here.
00:13:58.920 --> 00:14:00.910 Your
00:14:00.910 --> 00:14:02.476 This is what I personally use.
00:14:02.480 --> 00:14:05.978 You can use alternative
00:14:05.980 --> 00:14:08.598 The biggest thing is you have to
00:14:08.598 --> 00:14:11.100 make sure you're taking the
00:14:11.100 --> 00:14:13.316 Other people take
00:14:13.320 --> 00:14:16.218 Other people take
00:14:16.220 --> 00:14:18.152 It doesn't really matter the importance
00:14:18.152 --> 00:14:20.380 I find of using teams is again,
00:14:20.380 --> 00:14:22.270 if it's a recurring meeting,
00:14:22.270 --> 00:14:24.262 you'll actually see that
00:14:24.262 --> 00:14:26.254 reoccurring meeting multiple times,
00:14:26.260 --> 00:14:28.572 and you'll be able to pull it
00:14:28.572 --> 00:14:29.370 up relatively easily.
00:14:31.420 --> 00:14:34.564 While taking
00:14:34.564 --> 00:14:37.202 to delineate everything via bullet points,
00:14:37.202 --> 00:14:38.618 which thankfully meeting
00:14:38.620 --> 00:14:41.497 makes pretty easy and I can actually
00:14:41.497 --> 00:14:44.459 show you here if I type in a dash,
00:14:44.460 --> 00:14:48.508 it automatically puts in.
00:14:48.510 --> 00:14:50.030 Dot I don't know what these are called,
00:14:50.030 --> 00:14:53.341 but anyways it will then functionally format
00:14:53.341 --> 00:14:56.080 everything based off of bullet points.
00:14:56.080 --> 00:14:58.658 That was the word I was looking for so that
00:14:58.658 --> 00:15:01.276 kind of gets into the next discussion.
00:15:01.280 --> 00:15:04.164 Uhm, and that's how to format
00:15:04.170 --> 00:15:07.500 I have a very rigid structure of how I format
00:15:10.770 --> 00:15:12.774 which is a broadly speaking title
00:15:12.774 --> 00:15:14.540 of what we're talking about.
00:15:14.540 --> 00:15:17.396 A very short summary if applicable.
00:15:17.400 --> 00:15:18.840 Sometimes it's not applicable,
00:15:18.840 --> 00:15:19.920 it's just like.
00:15:19.920 --> 00:15:22.377 What is what is this subject mean?
00:15:22.380 --> 00:15:22.801 Broadly?
00:15:22.801 --> 00:15:26.590 Oh, why are we talking about this subject up?
00:15:26.590 --> 00:15:28.275 And it's very important to
00:15:28.275 --> 00:15:29.623 provide it when necessary,
00:15:29.630 --> 00:15:31.322 and I would say most of the time it
00:15:31.322 --> 00:15:33.059 is going to be necessary because.
00:15:33.060 --> 00:15:34.284 How are people going to know
00:15:34.284 --> 00:15:35.100 what you're talking about?
00:15:35.100 --> 00:15:37.800 If your subject is just?
00:15:37.800 --> 00:15:41.024 Syspro and then after that you're just
00:15:41.024 --> 00:15:42.883 trying to keep up with the conversation
00:15:42.883 --> 00:15:45.310 like you should try and provide some context.
00:15:45.310 --> 00:15:46.576 Why are we talking about syspro?
00:15:46.580 --> 00:15:48.848 Are we talking about a specific
00:15:48.848 --> 00:15:49.982 entity within syspro?
00:15:49.990 --> 00:15:51.043 Is it products?
00:15:51.043 --> 00:15:52.096 Is it whatever?
00:15:52.100 --> 00:15:54.380 Why are we talking about this?
00:15:54.380 --> 00:15:55.958 The user dashboard?
00:15:55.958 --> 00:15:58.550 Is it because we're going over a
00:15:58.550 --> 00:16:00.090 specific component of the user?
00:16:00.090 --> 00:16:01.986 Dashboard gives some context
00:16:01.986 --> 00:16:04.356 because a pretend that whoever
00:16:04.356 --> 00:16:06.896 is going to read these
00:16:06.900 --> 00:16:08.740 He's gonna need to not
00:16:08.740 --> 00:16:10.580 be included in the call.
00:16:10.580 --> 00:16:10.900 UM,
00:16:10.900 --> 00:16:13.780 a big portion of why I'm hammering on meeting
00:16:16.595 --> 00:16:18.220 Chris likes to say yeah,
00:16:18.220 --> 00:16:21.756 you can go back and review the recording.
00:16:21.760 --> 00:16:23.362 I might as well have been on the call
00:16:23.362 --> 00:16:24.980 if I have to review the recording,
00:16:24.980 --> 00:16:26.564 which is not helpful,
00:16:26.564 --> 00:16:28.544 so please please be taking
00:16:30.640 --> 00:16:32.395 It's also helpful to provide
00:16:32.395 --> 00:16:33.799 summaries because chances are
00:16:33.799 --> 00:16:35.694 you're going to forget why we even
00:16:35.694 --> 00:16:37.610 talked about it in the first place.
00:16:37.610 --> 00:16:40.170 Uh, and so it's useful to, uh,
00:16:40.170 --> 00:16:42.570 to bring up a specific summary
00:16:42.570 --> 00:16:44.090 of what's going on.
00:16:44.090 --> 00:16:45.910 So I gave an example for a
00:16:45.910 --> 00:16:46.690 header of Products,
00:16:46.690 --> 00:16:47.031 Inc.
00:16:47.031 --> 00:16:48.736 An example of issues noticing
00:16:48.736 --> 00:16:50.820 the products anchor due to lack
00:16:50.820 --> 00:16:52.460 of information on product kits,
00:16:52.460 --> 00:16:53.828 and I could probably
00:16:53.828 --> 00:16:55.196 simplify that way better.
00:16:55.200 --> 00:16:55.588 Uhm,
00:16:55.588 --> 00:16:57.916 and then the next portion is
00:16:57.916 --> 00:16:59.447 elaboration and discussion, so.
00:16:59.447 --> 00:17:02.016 There's multiple ways you can do this,
00:17:02.020 --> 00:17:02.272 uh,
00:17:02.272 --> 00:17:04.288 what I've seen a lot of people do
00:17:04.288 --> 00:17:06.369 is basically try to transcribe.
00:17:06.370 --> 00:17:06.728 UM,
00:17:06.728 --> 00:17:08.518 I'll be honest of everybody
00:17:08.518 --> 00:17:11.107 on here that I've seen tried
00:17:11.107 --> 00:17:12.730 to transcribe information.
00:17:12.730 --> 00:17:15.160 The only person I've ever seen
00:17:15.160 --> 00:17:16.780 do it really well.
00:17:16.780 --> 00:17:18.740 That I know of and that doesn't
00:17:18.740 --> 00:17:20.225 include Caroline or Sam 'cause
00:17:20.225 --> 00:17:21.680 I've never seen his
00:17:21.680 --> 00:17:24.480 The only person I've seen do it well is Kyle,
00:17:24.480 --> 00:17:27.175 and I can firmly tell you Kyle
00:17:27.175 --> 00:17:28.730 wasn't always that way.
00:17:28.730 --> 00:17:30.375 I worked with him in the office.
00:17:30.380 --> 00:17:34.734 He's gotten so fantastic about it that
00:17:34.734 --> 00:17:38.707 dude could record a a court session.
00:17:38.710 --> 00:17:42.118 So my advice, when getting into
00:17:42.118 --> 00:17:44.390 elaboration and discussion points,
00:17:44.390 --> 00:17:47.230 try to avoid trying to transcribe every word.
00:17:47.230 --> 00:17:49.366 Go short forming it. You know.
00:17:49.370 --> 00:17:51.995 Just mention the clients indicating
00:17:51.995 --> 00:17:54.004 this clarity. Dev stated this.
00:17:54.004 --> 00:17:57.099 You don't have to get into that much detail.
00:17:57.100 --> 00:17:58.232 What's really important is
00:17:58.232 --> 00:17:59.647 you're just trying to capture,
00:17:59.650 --> 00:18:03.507 broadly speaking, what did we go over?
00:18:03.510 --> 00:18:04.822 For any new PM's,
00:18:04.822 --> 00:18:07.219 and I would say that's half of
00:18:07.219 --> 00:18:10.420 the people here, if not more.
00:18:10.420 --> 00:18:12.208 It's really difficult for you guys
00:18:12.208 --> 00:18:14.162 to know what one information is
00:18:14.162 --> 00:18:16.612 important to write down and what isn't.
00:18:16.620 --> 00:18:18.398 You're going to pick that up overtime,
00:18:18.400 --> 00:18:19.420 but broadly speaking,
00:18:19.420 --> 00:18:21.460 if you can get more information,
00:18:21.460 --> 00:18:22.894 that's better information.
00:18:22.894 --> 00:18:25.762 What will happen during this discussion
00:18:25.762 --> 00:18:28.175 with the client is the client may
00:18:28.175 --> 00:18:30.359 say one thing and they're like,
00:18:30.360 --> 00:18:30.579 yeah,
00:18:30.579 --> 00:18:32.550 we think it's going to work this way and
00:18:32.606 --> 00:18:34.657 then suddenly the client will say actually,
00:18:34.660 --> 00:18:35.776 now that I think about it,
00:18:35.780 --> 00:18:37.250 it won't work that way.
00:18:37.250 --> 00:18:38.955 That can be really frustrating
00:18:38.955 --> 00:18:41.335 when trying to type all this down
00:18:41.335 --> 00:18:43.456 so it can be helpful if you're
00:18:43.456 --> 00:18:45.838 willing to try and slow down the
00:18:45.838 --> 00:18:47.536 conversation and maybe recap it,
00:18:47.536 --> 00:18:49.316 let people know like OK,
00:18:49.320 --> 00:18:51.615 so we think it's actually going to be this
00:18:51.615 --> 00:18:54.087 way that the product sync is going to work.
00:18:54.090 --> 00:18:56.239 Uhm so again try and reform it
00:18:56.239 --> 00:18:58.706 into your own words if possible and
00:18:58.706 --> 00:19:00.920 repeating it back to the client
00:19:00.997 --> 00:19:03.229 can be extremely useful as well.
00:19:03.230 --> 00:19:04.426 Uh, the last thing,
00:19:04.426 --> 00:19:06.220 and this is arguably the most
00:19:06.288 --> 00:19:08.000 important thing about
00:19:08.000 --> 00:19:09.784 Are the action items.
00:19:09.784 --> 00:19:10.230 Again,
00:19:10.230 --> 00:19:12.491 I'm noticing a lot of people are
00:19:12.491 --> 00:19:14.390 not writing down action items.
00:19:14.390 --> 00:19:16.380 When I joined the company,
00:19:16.380 --> 00:19:20.108 we had a PM here who was just for
00:19:20.108 --> 00:19:22.964 fanatic about taking down action items.
00:19:22.970 --> 00:19:24.490 Everything was recorded into action
00:19:24.490 --> 00:19:26.010 items and everything was recorded
00:19:26.058 --> 00:19:27.468 for action items for the client.
00:19:27.470 --> 00:19:28.722 Action items for clarity,
00:19:28.722 --> 00:19:30.287 action items for this person,
00:19:30.290 --> 00:19:31.386 action for that person,
00:19:31.386 --> 00:19:33.360 and when I first joined us like.
00:19:33.360 --> 00:19:35.625 And that seems like busywork
00:19:35.625 --> 00:19:37.437 like that's so unnecessary.
00:19:37.440 --> 00:19:40.150 I do it for all my projects now and it
00:19:40.228 --> 00:19:42.796 took me probably a year to learn the
00:19:42.796 --> 00:19:45.658 hard way why he was doing it like that,
00:19:45.660 --> 00:19:47.658 having action items and more specifically,
00:19:47.660 --> 00:19:51.710 Bolding the action items is incredibly
00:19:51.710 --> 00:19:55.489 helpful with making sure that the.
00:19:55.490 --> 00:19:57.760 Client and you know what
00:19:57.760 --> 00:19:59.576 needs to happen next.
00:19:59.580 --> 00:20:00.905 They can be copied and
00:20:00.905 --> 00:20:01.965 pasted into your agenda,
00:20:01.970 --> 00:20:03.650 so they're useful for that.
00:20:03.650 --> 00:20:05.755 They're also useful because I'll
00:20:05.755 --> 00:20:07.018 mention this later.
00:20:07.020 --> 00:20:09.476 You can turn them into tattoos on base
00:20:09.476 --> 00:20:11.791 camp so that the client knows that
00:20:11.791 --> 00:20:14.159 they need to follow up with this.
00:20:14.160 --> 00:20:15.936 You can provide your
00:20:15.936 --> 00:20:17.739 to the client and tell them.
00:20:17.740 --> 00:20:20.680 Please review the bolded items.
00:20:20.680 --> 00:20:23.565 A lot of that's incredibly
00:20:23.565 --> 00:20:25.298 important to the client,
00:20:25.298 --> 00:20:27.321 but it's also very useful for you
00:20:27.321 --> 00:20:29.478 to be able to organize your work.
00:20:29.480 --> 00:20:30.828 So again.
00:20:30.828 --> 00:20:35.546 Try and provide some sort of summary.
00:20:35.550 --> 00:20:38.446 Provide some title of what the subject is.
00:20:38.450 --> 00:20:40.284 Go over and elaborate what the discussion
00:20:40.284 --> 00:20:42.483 is and then get into the action items and
00:20:42.483 --> 00:20:44.656 I'll bring up an example here in a little
00:20:44.656 --> 00:20:46.730 bit and show you exactly how I plan to do.
00:20:46.730 --> 00:20:48.720 A lot of this saving.
00:20:48.720 --> 00:20:51.989 So where does save the meeting
00:20:51.990 --> 00:20:54.726 Again using the template provided above,
00:20:54.730 --> 00:20:56.956 my overall way of doing this and
00:20:56.956 --> 00:20:59.408 this again was something from Kevin,
00:20:59.410 --> 00:21:02.738 so if you have any questions on it.
00:21:02.740 --> 00:21:04.252 Reference back to me,
00:21:04.252 --> 00:21:06.142 but Kevin Cramer is definitely
00:21:06.142 --> 00:21:07.639 going to know as well.
00:21:07.640 --> 00:21:10.820 Try to format the title of it as a year,
00:21:10.820 --> 00:21:12.065 month, date, client,
00:21:12.065 --> 00:21:14.140 acronym and then project status,
00:21:14.140 --> 00:21:16.966 meeting
00:21:16.970 --> 00:21:18.110 So an example here is
00:21:20.660 --> 00:21:23.908 2020 10901 IOM is the project acronym
00:21:23.908 --> 00:21:27.189 and then project status meeting
00:21:27.190 --> 00:21:29.560 My recommendation is if I go
00:21:29.560 --> 00:21:31.980 and I can actually show you.
00:21:31.980 --> 00:21:34.536 Today I had a meeting with a animal care
00:21:34.536 --> 00:21:36.949 and we took down some meeting
00:21:36.950 --> 00:21:38.966 So here's all my
00:21:38.966 --> 00:21:40.460 them exactly the way I mentioned.
00:21:40.460 --> 00:21:44.226 So we just talked about lifecycle workflows.
00:21:44.230 --> 00:21:47.715 I went through and thankfully again, Kyle
00:21:47.715 --> 00:21:50.235 is also the same level of like organized,
00:21:50.240 --> 00:21:54.356 so he had everything via user stories.
00:21:54.360 --> 00:21:55.670 So I created my subjects
00:21:55.670 --> 00:21:56.980 based on those user stories.
00:21:56.980 --> 00:21:58.516 So we're going over product school.
00:21:58.520 --> 00:22:00.075 This is the product section
00:22:00.075 --> 00:22:01.319 going over customers cool.
00:22:01.320 --> 00:22:02.340 Here's the customer section.
00:22:02.340 --> 00:22:03.574 Sales order, invoices, memos.
00:22:03.574 --> 00:22:06.470 UM then I go through and I add
00:22:06.550 --> 00:22:09.170 either an additional subject line.
00:22:09.170 --> 00:22:11.156 So this is a specific discussion,
00:22:11.160 --> 00:22:13.724 or it provides the.
00:22:13.724 --> 00:22:14.148 Context,
00:22:14.148 --> 00:22:17.540 so the workflows of SAGE 100 to Sage
00:22:17.626 --> 00:22:20.594 CRM will remain the same as the
00:22:20.594 --> 00:22:23.309 workflows for Sage 100 and HubSpot.
00:22:23.310 --> 00:22:25.088 Some of these don't require action items,
00:22:25.090 --> 00:22:26.368 'cause this is a discovery meeting.
00:22:26.370 --> 00:22:29.280 It's just taking down information.
00:22:29.280 --> 00:22:31.092 In other scenarios, UM,
00:22:31.092 --> 00:22:32.904 you'll need action items,
00:22:32.910 --> 00:22:35.227 so down here we need more clarification
00:22:35.227 --> 00:22:37.524 on how to manage which HubSpot
00:22:37.524 --> 00:22:39.172 instance that we're actually
00:22:39.172 --> 00:22:41.712 going to be integrating data too.
00:22:41.712 --> 00:22:45.699 So there's a action item for them to confirm.
00:22:45.700 --> 00:22:47.680 If Sage 100 instances are separated
00:22:47.680 --> 00:22:50.125 so that clarity connect can pull data
00:22:50.125 --> 00:22:51.905 directly from that singular instance,
00:22:51.910 --> 00:22:55.708 and no additional logic need apply.
00:22:55.710 --> 00:22:58.097 So a delineated at all by this.
00:22:58.100 --> 00:22:59.584 Every time I type in action item,
00:22:59.590 --> 00:23:01.840 I make sure to bold it so I can come
00:23:01.910 --> 00:23:04.223 back to it after the end of the call.
00:23:04.230 --> 00:23:05.958 Once I have my
00:23:05.960 --> 00:23:07.955 This is obviously only useful for me.
00:23:07.960 --> 00:23:11.686 So what I'll next do is I'll pull up
00:23:11.686 --> 00:23:13.780 the and if you're not using SharePoint,
00:23:13.780 --> 00:23:14.884 you should be.
00:23:14.884 --> 00:23:17.092 I'll pull up my SharePoint Files
00:23:17.092 --> 00:23:19.298 Go to the specific project,
00:23:19.300 --> 00:23:21.820 project management, meeting
00:23:21.820 --> 00:23:25.620 I have this meeting
00:23:25.620 --> 00:23:30.250 Open this one back up a I can pull up the.
00:23:30.250 --> 00:23:32.476 Teams and pulled up the wrong thing.
00:23:34.560 --> 00:23:38.430 And then I just have to copy and paste.
00:23:38.430 --> 00:23:40.836 Simple enough. Uhm, I would recommend
00:23:40.836 --> 00:23:43.450 getting rid of the bullet point.
00:23:43.450 --> 00:23:46.908 You'll have to paste without the format
00:23:46.910 --> 00:23:49.094 or match the format that's already there.
00:23:49.100 --> 00:23:51.158 But look all my meeting
00:23:51.158 --> 00:23:52.896 there and already formatted the way
00:23:52.896 --> 00:23:54.765 I need them to be printed Genda.
00:23:54.770 --> 00:23:56.926 Since this was our first discovery meeting,
00:23:56.930 --> 00:23:59.261 you know you can just type out
00:23:59.261 --> 00:24:00.588 lifecycle workflows, mappings,
00:24:00.588 --> 00:24:03.878 credentials so on so forth.
00:24:03.880 --> 00:24:05.455 Again, format it.
00:24:05.455 --> 00:24:10.570 In this case, care animal care.
00:24:10.570 --> 00:24:13.100 This is a discovery meeting.
00:24:13.100 --> 00:24:14.420 So I'll just indicate that.
00:24:16.840 --> 00:24:18.850 Every. And then of course put
00:24:18.850 --> 00:24:21.198 in the date which it was today.
00:24:23.210 --> 00:24:25.694 Up here you can change the title and that's
00:24:25.694 --> 00:24:27.820 exactly what I'm going to do so 2021.
00:24:30.450 --> 00:24:32.902 09.03 care. Discovery. Simple,
00:24:32.902 --> 00:24:38.210 it took me less than a minute to do.
00:24:38.210 --> 00:24:39.850 I have meeting
00:24:39.850 --> 00:24:42.274 The next step I would recommend is copying
00:24:42.274 --> 00:24:44.605 and pasting your meeting
00:24:44.605 --> 00:24:46.810 then taking them to the actual channel
00:24:46.810 --> 00:24:49.467 so it's already saved into the channel.
00:24:49.470 --> 00:24:51.576 I find this very, very useful.
00:24:51.580 --> 00:24:54.164 And honestly if you don't find this useful,
00:24:54.170 --> 00:24:55.462 I'd be very shocked.
00:24:55.462 --> 00:24:58.077 But anybody who's on any of my projects
00:24:58.077 --> 00:25:00.565 knows I do this all at general.
00:25:00.565 --> 00:25:03.115 I haven't personally got a complaint.
00:25:03.120 --> 00:25:04.570 I could see people complaining
00:25:04.570 --> 00:25:05.770 'cause it's like, oh,
00:25:05.770 --> 00:25:08.410 you're at generally the whole the whole team,
00:25:08.410 --> 00:25:09.950 but I'm basically just copying,
00:25:09.950 --> 00:25:12.176 pasting my meeting
00:25:12.180 --> 00:25:14.826 Uh, now in this specific example,
00:25:14.830 --> 00:25:16.690 most likely this is going to
00:25:16.690 --> 00:25:18.609 be more useful to say Kyle,
00:25:18.610 --> 00:25:20.114 so he can look at my
00:25:20.114 --> 00:25:21.320 Brian Lee for that matter.
00:25:21.320 --> 00:25:23.874 He can look at my
00:25:23.874 --> 00:25:26.880 Yep, this is. This is what my
00:25:26.880 --> 00:25:29.224 It's basically word for word the same thing,
00:25:29.230 --> 00:25:31.250 but for project status meetings
00:25:31.250 --> 00:25:33.700 and certainly for where we have
00:25:33.700 --> 00:25:35.500 action items for the devs.
00:25:35.500 --> 00:25:37.360 My next goal would be to,
00:25:37.360 --> 00:25:39.860 uh, make sure that, uhm,
00:25:39.860 --> 00:25:42.597 I'm also attaching different people to this.
00:25:42.600 --> 00:25:44.320 So after I post this,
00:25:44.320 --> 00:25:46.498 which again I just do twenty
00:25:46.500 --> 00:25:49.004 2109 or three care.
00:25:49.004 --> 00:25:51.508 Project A discovery meeting.
00:25:56.210 --> 00:25:58.863 State, let's say I have an action
00:25:58.863 --> 00:26:01.128 item for Eric Cool at Eric.
00:26:01.130 --> 00:26:04.476 Copy and paste the actual action item.
00:26:04.480 --> 00:26:05.656 They're easy enough again.
00:26:05.656 --> 00:26:07.910 It took me less than a minute,
00:26:07.910 --> 00:26:10.129 but it means that I know I've
00:26:10.129 --> 00:26:11.900 done everything I need to do.
00:26:11.900 --> 00:26:13.741 To get everybody that needs to be
00:26:13.741 --> 00:26:15.877 on the same page on the same page,
00:26:15.880 --> 00:26:17.878 there are scenarios where it's useful
00:26:17.878 --> 00:26:20.379 and I would say probably 9 times out
00:26:20.379 --> 00:26:22.990 of 10 it would be great to post meeting
00:26:25.900 --> 00:26:27.580 Again, highly recommend following
00:26:27.580 --> 00:26:29.734 this format how they recommend
00:26:29.734 --> 00:26:32.116 copying and pasting this into a
00:26:32.120 --> 00:26:34.624 basecamp message if possible.
00:26:34.624 --> 00:26:37.836 That said, the utility of that can fall
00:26:37.836 --> 00:26:40.107 apart pretty quickly because a lot of
00:26:40.107 --> 00:26:42.382 clients don't actually care, be you.
00:26:42.382 --> 00:26:45.568 The additional time you spend 'cause,
00:26:45.570 --> 00:26:47.232 let's say this all adds up
00:26:47.232 --> 00:26:48.890 to an additional 15 minutes.
00:26:48.890 --> 00:26:51.130 Yeah, that that may not be times that
00:26:51.130 --> 00:26:53.160 the client necessarily cares about.
00:26:53.160 --> 00:26:54.972 So there are times where you'll
00:26:54.972 --> 00:26:57.362 want to save it to teams and also
00:26:57.362 --> 00:26:58.752 save it to base camp.
00:26:58.760 --> 00:27:01.088 My general best practice for following
00:27:01.088 --> 00:27:04.439 up is to create A to do when applicable.
00:27:04.440 --> 00:27:06.610 Now, because we're in discovery
00:27:06.610 --> 00:27:08.346 for that specific project,
00:27:08.350 --> 00:27:11.206 I'm not as worried about them
00:27:11.210 --> 00:27:13.380 following up for you know,
00:27:13.380 --> 00:27:14.480 all their action items,
00:27:14.480 --> 00:27:17.030 but once we get into project status meetings,
00:27:17.030 --> 00:27:18.794 and potentially there's
00:27:18.794 --> 00:27:20.558 blockers and development,
00:27:20.560 --> 00:27:22.810 if that developer has a block
00:27:22.810 --> 00:27:24.740 and they need something done,
00:27:24.740 --> 00:27:27.620 you have to be as a PM the
00:27:27.620 --> 00:27:29.343 person to create todo's.
00:27:29.343 --> 00:27:31.767 In base camp and make sure they happen.
00:27:31.770 --> 00:27:34.346 Arguably and again, since we're in discovery,
00:27:34.350 --> 00:27:35.718 I'm not as pressed about it,
00:27:35.720 --> 00:27:37.784 but arguably your to do should
00:27:37.784 --> 00:27:39.730 have due dates on them.
00:27:39.730 --> 00:27:41.730 Make sure people know about
00:27:41.730 --> 00:27:43.797 things that have to be done.
00:27:43.800 --> 00:27:47.210 Again, the client will be.
00:27:47.210 --> 00:27:48.630 Overall benefiting from this,
00:27:48.630 --> 00:27:51.226 but it also means that there's less
00:27:51.226 --> 00:27:53.246 likelihood of the timeline slipping.
00:27:53.250 --> 00:27:54.562 People being upset because,
00:27:54.562 --> 00:27:56.906 well, I wasn't even told this was
00:27:56.906 --> 00:27:59.020 a thing that was blocking.
00:27:59.020 --> 00:28:00.502 And if you're really pressed for
00:28:00.502 --> 00:28:01.490 time and you're like,
00:28:01.490 --> 00:28:02.702 oh I'm too busy,
00:28:02.702 --> 00:28:04.520 ask the developer or resource you're
00:28:04.583 --> 00:28:06.466 working with or Kyle or Brian Lee
00:28:06.466 --> 00:28:08.520 asked them if they might be able
00:28:08.520 --> 00:28:10.302 to help you create those tattoos.
00:28:10.310 --> 00:28:11.500 You can delegate the work,
00:28:11.500 --> 00:28:12.680 and I certainly do it.
00:28:12.680 --> 00:28:15.200 Probably more than any other PM team member,
00:28:15.200 --> 00:28:16.788 but delegate the work.
00:28:16.788 --> 00:28:19.170 Ask people to create base camp
00:28:19.250 --> 00:28:20.450 to do's for you,
00:28:20.450 --> 00:28:22.664 provide a summary of what the action item is,
00:28:22.670 --> 00:28:24.700 assign it to the relevant team members,
00:28:24.700 --> 00:28:26.164 and then, when done,
00:28:26.164 --> 00:28:27.994 make sure everybody who needs
00:28:27.994 --> 00:28:29.809 to know knows about it.
00:28:29.810 --> 00:28:31.588 If you don't know about Basecamp tattoos,
00:28:31.590 --> 00:28:33.324 you should also consider making sure
00:28:33.324 --> 00:28:35.430 that you're on the subscribers list,
00:28:35.430 --> 00:28:37.686 'cause if they reply to that
00:28:37.686 --> 00:28:38.814 discussion in Basecamp,
00:28:38.820 --> 00:28:42.095 it will almost certainly not
00:28:42.095 --> 00:28:43.950 a you won't know about it,
00:28:43.950 --> 00:28:45.546 because if you didn't create the
00:28:45.546 --> 00:28:47.552 base camp to do and you're not
00:28:47.552 --> 00:28:48.724 only assigned to list.
00:28:48.730 --> 00:28:51.054 He won't be on the subscribers list.
00:28:51.060 --> 00:28:54.938 So attached down here I added this
00:28:54.940 --> 00:28:58.070 cut project status meeting again.
00:28:58.070 --> 00:28:59.610 You're more than welcome to go through
00:28:59.610 --> 00:29:01.280 all my projects and see if I don't
00:29:01.280 --> 00:29:02.610 have meeting
00:29:02.610 --> 00:29:03.786 I'm certain there's probably
00:29:03.786 --> 00:29:05.550 some edge cases where I don't,
00:29:05.550 --> 00:29:09.230 but I try to take as much detail as I can,
00:29:09.230 --> 00:29:10.770 but again, per subject.
00:29:10.770 --> 00:29:14.630 I'm only taking in, you know, a subject.
00:29:14.630 --> 00:29:17.366 Very short summary. What's the output?
00:29:17.366 --> 00:29:19.026 Sometimes there isn't even a
00:29:19.026 --> 00:29:21.010 purpose in adding in discussions.
00:29:21.010 --> 00:29:21.862 It's a question.
00:29:21.862 --> 00:29:23.566 What's the answer to the question?
00:29:23.570 --> 00:29:25.873 We don't need to record every single
00:29:25.873 --> 00:29:28.310 detail of the discussion unless it.
00:29:28.310 --> 00:29:31.328 You know is producing additional questions,
00:29:31.330 --> 00:29:33.562 uh? But go through and record
00:29:33.562 --> 00:29:35.689 the information as best you can.
00:29:35.690 --> 00:29:38.340 I find this incredibly readable,
00:29:38.340 --> 00:29:40.720 so if you don't know how to format this way,
00:29:40.720 --> 00:29:42.526 it's bullet points.
00:29:42.526 --> 00:29:46.860 Then you press enter and then tab to
00:29:46.860 --> 00:29:49.260 create an additional bullet point.
00:29:49.260 --> 00:29:51.724 So again, I find it very useful.
00:29:51.730 --> 00:29:53.968 I personally find this more readable,
00:29:53.970 --> 00:29:55.760 the action items being bolded
00:29:55.760 --> 00:29:57.550 stick out to me more.
00:29:57.550 --> 00:29:59.863 If you have a better way of formatting it,
00:29:59.870 --> 00:30:00.432 prove it.
00:30:00.432 --> 00:30:02.399 I want to see the meeting
00:30:02.400 --> 00:30:04.591 I want to see how they're they're
00:30:04.591 --> 00:30:06.627 working and then we collectively can
00:30:06.627 --> 00:30:09.035 decide to change to a newer format.
00:30:09.040 --> 00:30:11.302 But if you're not using this
00:30:11.302 --> 00:30:13.040 format and this is something I
00:30:13.040 --> 00:30:14.400 talked with Kelsey with Caroline,
00:30:14.400 --> 00:30:15.640 I believe you and I talked about it,
00:30:15.640 --> 00:30:17.516 but I know I talked with Kelsey.
00:30:17.520 --> 00:30:19.350 If you're not using this format,
00:30:19.350 --> 00:30:22.656 this will probably be affecting you.
00:30:22.660 --> 00:30:25.426 Know how your your monthly audits
00:30:25.426 --> 00:30:27.270 are impacted and potentially
00:30:27.352 --> 00:30:28.990 even your performance.
00:30:28.990 --> 00:30:31.555 I can tell you first hand if you're not.
00:30:31.560 --> 00:30:32.910 Recording information you're
00:30:32.910 --> 00:30:34.710 not taking action items,
00:30:34.710 --> 00:30:37.140 and you're not accurately getting those
00:30:37.140 --> 00:30:40.218 information to the to the necessary people.
00:30:40.220 --> 00:30:43.868 You will likely fall behind on the project
00:30:43.870 --> 00:30:47.118 and you can blame any number of factors.
00:30:47.120 --> 00:30:51.146 But it'll make everything disorganized and.
00:30:51.150 --> 00:30:53.315 As the project status or
00:30:53.315 --> 00:30:55.047 as the project manager,
00:30:55.050 --> 00:30:58.070 it's going to fall to you to own up to that.
00:30:58.070 --> 00:30:59.869 So I have my action items or
00:30:59.869 --> 00:31:01.892 sorry I have my uh, example here.
00:31:01.892 --> 00:31:04.328 Feel free to pick through it.
00:31:04.330 --> 00:31:05.910 Feel free to take a look at how we do it.
00:31:05.910 --> 00:31:09.470 I have my meeting
00:31:09.470 --> 00:31:10.286 read through this.
00:31:10.286 --> 00:31:11.918 This is what I would consider
00:31:11.918 --> 00:31:13.159 to be a good policy.
00:31:13.160 --> 00:31:13.874 That said,
00:31:13.874 --> 00:31:16.016 I'm not afraid of you guys
00:31:16.016 --> 00:31:17.843 coming in and saying, hey,
00:31:17.843 --> 00:31:19.580 I think we should change it or I think
00:31:19.633 --> 00:31:21.388 we should do this or I think we should,
00:31:21.390 --> 00:31:21.894 you know,
00:31:21.894 --> 00:31:23.406 but you should be proving it.
00:31:23.410 --> 00:31:24.964 You should be taking those
00:31:24.964 --> 00:31:26.988 and we need to be seeing those
00:31:26.988 --> 00:31:28.220 nodes added into teams.
00:31:28.220 --> 00:31:30.320 Uh, if you're not taking meeting
00:31:30.320 --> 00:31:31.468 consider this.
00:31:31.468 --> 00:31:35.486 An initiative to start doing that now.
00:31:35.490 --> 00:31:37.346 So that was a lot, UM,
00:31:37.346 --> 00:31:40.958 but I wanted to engage, uh,
00:31:40.958 --> 00:31:42.670 how does everybody feel?
00:31:42.670 --> 00:31:44.680 And I know Stephanie is away,
00:31:44.680 --> 00:31:48.505 so this is really just gonna fall to PJ,
00:31:48.510 --> 00:31:52.600 Kevin Santiago, Eric, Brian Lee.
00:31:52.600 --> 00:31:54.808 And of course Caroline and Sam
00:31:54.808 --> 00:31:56.910 if y'all have anything as well.
00:31:56.910 --> 00:32:00.050 Yeah, it's a standard format, uhm,
00:32:00.050 --> 00:32:03.690 I've used the template in the past.
00:32:03.690 --> 00:32:07.050 And then I kind of got out of the habit.
00:32:07.050 --> 00:32:09.564 Simply because when meetings are stacked
00:32:09.564 --> 00:32:15.280 back to back to back, yeah yeah.
00:32:15.280 --> 00:32:16.765 And honestly, people,
00:32:16.765 --> 00:32:19.735 people will complain and they do.
00:32:19.740 --> 00:32:22.060 And I know and I've just pushed back on it.
00:32:22.060 --> 00:32:23.818 I've gotten complaints that I don't.
00:32:23.820 --> 00:32:26.879 I don't sit back to back meetings.
00:32:26.880 --> 00:32:29.057 I just like there's one exception here,
00:32:29.060 --> 00:32:31.630 and it's because I was.
00:32:31.630 --> 00:32:34.507 Well, there's one exception here because MGS,
00:32:34.510 --> 00:32:35.750 like a 15 minute meeting,
00:32:35.750 --> 00:32:36.638 no matter what.
00:32:36.638 --> 00:32:38.710 So I always have time after that.
00:32:38.710 --> 00:32:41.212 But it was also because that was the only
00:32:41.212 --> 00:32:43.486 time where I could get like 5 internal
00:32:43.486 --> 00:32:45.870 people on the same call with the client.
00:32:45.870 --> 00:32:49.014 I do have back to back internal meetings,
00:32:49.020 --> 00:32:50.970 but usually those are more flexible.
00:32:50.970 --> 00:32:52.945 And as Eric Negrete and
00:32:52.945 --> 00:32:54.525 my connect team knows,
00:32:54.530 --> 00:32:58.170 I'm move them around a lot and sometimes
00:32:58.170 --> 00:33:00.250 come late to a lot of internal meetings,
00:33:00.250 --> 00:33:02.374 but I don't I.
00:33:02.374 --> 00:33:04.024 Absolutely refuse, if possible,
00:33:04.024 --> 00:33:06.068 to have back to back client meetings,
00:33:06.070 --> 00:33:08.625 and that is difficult to navigate to
00:33:08.625 --> 00:33:11.005 tell your client like I think you
00:33:11.005 --> 00:33:15.998 know I I can't do like I, I won't do.
00:33:15.998 --> 00:33:19.258 1:30, uh, because I know it's following this.
00:33:19.260 --> 00:33:21.424 Eric's meeting. I won't do, you know.
00:33:21.424 --> 00:33:23.596 12:00 o'clock because I know it's
00:33:23.596 --> 00:33:25.639 immediately after this West call, UM.
00:33:25.639 --> 00:33:28.222 But that's to give myself some more
00:33:28.222 --> 00:33:31.237 time to actually format those
00:33:31.240 --> 00:33:31.675 Again,
00:33:31.675 --> 00:33:33.850 there are exceptions where it's
00:33:33.850 --> 00:33:35.155 like discraft MG.
00:33:35.160 --> 00:33:37.278 Those meetings are usually incredibly short,
00:33:37.280 --> 00:33:37.652 but.
00:33:37.652 --> 00:33:38.024 Yeah,
00:33:38.024 --> 00:33:41.000 I I always bake in extra time into
00:33:41.085 --> 00:33:43.977 my schedule just for meeting
00:33:43.980 --> 00:33:47.250 Yeah, I like that, that's good.
00:33:47.250 --> 00:33:47.850 And again,
00:33:47.850 --> 00:33:49.350 I I totally understand where
00:33:49.350 --> 00:33:50.250 you're coming from.
00:33:50.250 --> 00:33:53.472 PJ 'cause I 1000% dealt with the same thing.
00:33:53.480 --> 00:33:57.134 I just got really good at telling people no.
00:33:57.140 --> 00:33:58.616 Hey can we have this meeting at this time?
00:33:58.620 --> 00:34:00.594 It's like no sorry I I need
00:34:00.594 --> 00:34:02.427 to make sure that XY and Z.
00:34:02.427 --> 00:34:03.681 And honestly if you gotta make
00:34:03.681 --> 00:34:05.018 something out and make something up,
00:34:05.020 --> 00:34:07.792 but I always bake in some time
00:34:07.792 --> 00:34:08.980 into your schedule.
00:34:08.980 --> 00:34:09.305 Ironically,
00:34:09.305 --> 00:34:11.255 developers seem to be the opposite.
00:34:11.260 --> 00:34:13.269 Eric Weathers loves back to back meetings,
00:34:13.270 --> 00:34:14.098 which is understandable.
00:34:14.098 --> 00:34:15.754 It's hard for them to code
00:34:15.760 --> 00:34:17.716 in between meetings.
00:34:17.716 --> 00:34:19.020 Yeah, yeah,
00:34:19.020 --> 00:34:19.788 that makes sense.
00:34:22.130 --> 00:34:23.859 Any other comments or anything like that?
00:34:25.890 --> 00:34:28.700 Participants for meeting
00:34:28.700 --> 00:34:32.662 like adding those, or should we not?
00:34:32.662 --> 00:34:34.174 Participants, what do you mean
00:34:34.174 --> 00:34:35.960 like who was in a meeting, right?
00:34:35.960 --> 00:34:37.440 Like discovery, you know?
00:34:37.440 --> 00:34:40.220 I mean, you had come.
00:34:40.220 --> 00:34:42.626 Yeah, people from whatever that company
00:34:42.626 --> 00:34:45.990 was and then he had Kyle me and you or.
00:34:45.990 --> 00:34:48.014 Kickoffs and I can go over the kickoff
00:34:48.014 --> 00:34:49.442 agenda, maybe on another training.
00:34:49.442 --> 00:34:52.594 I only do that on the kickoffs, because, uh,
00:34:52.594 --> 00:34:56.270 I want to make sure I understand their roles.
00:34:56.270 --> 00:34:58.240 But usually like I mean,
00:34:58.240 --> 00:34:59.776 I guess it depends on how many people
00:34:59.776 --> 00:35:01.167 you have working on the project,
00:35:01.170 --> 00:35:03.312 but usually it's like you're only working
00:35:03.312 --> 00:35:05.360 with like three client team members.
00:35:05.360 --> 00:35:06.725 Like maybe there's more on the call,
00:35:06.730 --> 00:35:08.956 but those are your three deciders
00:35:08.956 --> 00:35:09.698 or whatever,
00:35:09.700 --> 00:35:11.443 so you get to know those peoples
00:35:11.443 --> 00:35:12.190 names pretty easily.
00:35:12.190 --> 00:35:14.248 You can absolutely do that starting off,
00:35:14.250 --> 00:35:16.458 and that's probably a good idea to keep.
00:35:16.460 --> 00:35:17.780 Track of things.
00:35:17.780 --> 00:35:20.845 I know Eric when he and I were working
00:35:20.845 --> 00:35:22.150 on handoffs for some projects.
00:35:22.150 --> 00:35:24.558 He's like I forget who's like what
00:35:24.558 --> 00:35:26.930 does Blake do on arrow financial
00:35:26.930 --> 00:35:29.331 like stuff like that totally 100%,
00:35:29.331 --> 00:35:31.659 but I mean that's a level of granularity.
00:35:31.660 --> 00:35:34.090 You probably won't need after you.
00:35:34.090 --> 00:35:36.230 After the initial stand up.
00:35:36.230 --> 00:35:38.348 Exactly, of course.
00:35:38.350 --> 00:35:38.720 Home.
00:35:41.750 --> 00:35:42.570 Anything else?
00:35:42.570 --> 00:35:45.850 Yeah, so actually I had a big one.
00:35:45.850 --> 00:35:48.966 There are some cases not really like
00:35:48.966 --> 00:35:50.796 that often in connected meetings,
00:35:50.800 --> 00:35:53.062 but in Seth sometimes we're doing
00:35:53.062 --> 00:35:55.493 demos and they might be mentioning
00:35:55.493 --> 00:35:58.055 things that are worth writing down.
00:35:58.060 --> 00:36:00.040 But I fear like constantly going
00:36:00.040 --> 00:36:02.605 back to jot down what they're saying
00:36:02.605 --> 00:36:04.951 and not walking through the demo
00:36:04.951 --> 00:36:07.297 might be a little too distracting.
00:36:07.300 --> 00:36:09.580 No, that would be the best
00:36:09.580 --> 00:36:11.650 way to go about that.
00:36:11.650 --> 00:36:12.724 I'm I'm very glad you brought
00:36:12.724 --> 00:36:13.780 that up and I didn't.
00:36:13.780 --> 00:36:16.258 I don't think I fully addressed it.
00:36:16.260 --> 00:36:19.842 I will straight up I'm gonna do it Kevin.
00:36:19.850 --> 00:36:20.632 Thank you.
00:36:20.632 --> 00:36:23.369 I will straight up stop the conversation.
00:36:23.370 --> 00:36:27.220 Give a full minute of awkward silence
00:36:27.220 --> 00:36:30.964 just so I can jot things down 100%.
00:36:30.964 --> 00:36:33.236 I do not like and I've never had
00:36:33.236 --> 00:36:35.518 a client complain about that.
00:36:35.520 --> 00:36:37.760 Never once have I ever had a client
00:36:37.760 --> 00:36:39.890 be like can we hurry up like I?
00:36:39.890 --> 00:36:40.926 It's a fear iPad,
00:36:40.926 --> 00:36:42.480 but it's never happened so it's
00:36:42.534 --> 00:36:44.118 like I'll straight up be like.
00:36:44.120 --> 00:36:45.625 OK guys, give me a few minutes.
00:36:45.630 --> 00:36:47.387 I'm going to make sure I know
00:36:47.387 --> 00:36:49.804 take this down and if you maybe
00:36:49.804 --> 00:36:51.468 when you're notating it,
00:36:51.470 --> 00:36:53.060 you're like and just to clarify,
00:36:53.060 --> 00:36:55.517 you met this or just to clarify,
00:36:55.520 --> 00:36:57.070 could you repeat one extra
00:36:57.070 --> 00:36:59.133 thing you had said prior, like?
00:36:59.133 --> 00:37:02.724 It's so important to do that because.
00:37:02.730 --> 00:37:04.428 Inadvertently, and I I don't mean
00:37:04.428 --> 00:37:05.870 this directing at you Eric,
00:37:05.870 --> 00:37:06.930 I just mean in general,
00:37:06.930 --> 00:37:09.044 if you're rushing through 'cause you're like,
00:37:09.050 --> 00:37:10.028 oh, get to the next point,
00:37:10.030 --> 00:37:11.422 gets the next point.
00:37:11.422 --> 00:37:12.814 Don't leave awkward silence.
00:37:12.820 --> 00:37:15.684 You will 1000% run into the scenario where
00:37:15.684 --> 00:37:18.696 you forget a thing and then the next meeting
00:37:18.700 --> 00:37:22.028 where they say didn't we talk about this?
00:37:22.030 --> 00:37:22.307 Ouch,
00:37:22.307 --> 00:37:24.523 that's where you're going to be in trouble,
00:37:24.530 --> 00:37:26.360 and that's it's gonna suck.
00:37:26.360 --> 00:37:26.818 Yeah,
00:37:26.818 --> 00:37:27.734 go ahead,
00:37:27.734 --> 00:37:28.192 Stephanie.
00:37:28.192 --> 00:37:28.650 Uh,
00:37:28.650 --> 00:37:30.810 just another quick call out to
00:37:30.810 --> 00:37:32.963 that is anytime you're doing a
00:37:32.963 --> 00:37:35.938 client demo and I have learned
00:37:35.938 --> 00:37:39.430 this lesson through death by 1000.
00:37:39.430 --> 00:37:42.755 Cuts through being raked over the coals
00:37:42.755 --> 00:37:46.078 and thrown into an exploding volcano.
00:37:46.080 --> 00:37:49.045 Record your demo beforehand and
00:37:49.045 --> 00:37:52.644 then leave time after the demo
00:37:52.644 --> 00:37:55.770 for going through and having a
00:37:55.770 --> 00:37:57.135 Q&A with your client so that you
00:37:57.135 --> 00:37:58.407 can sit there and be like OK.
00:37:58.410 --> 00:37:59.370 Well, let me write that down.
00:37:59.370 --> 00:38:01.860 Let me take a 8ccef38e-04f5-4020-80be-1b4f1739203e
00:38:01.860 --> 00:38:04.149 That way you don't feel that pressure
00:38:04.149 --> 00:38:06.670 to run this perfectly smooth demo.
00:38:06.670 --> 00:38:07.730 And then they're like, oh,
00:38:07.730 --> 00:38:09.389 but wait, can you just go back
00:38:09.389 --> 00:38:11.069 to this other screen over here?
00:38:11.070 --> 00:38:12.342 It's already recorded.
00:38:12.342 --> 00:38:13.190 There's no,
00:38:13.190 --> 00:38:16.889 there's no way to go back kind of thing.
00:38:16.890 --> 00:38:19.138 And then you can do that with them,
00:38:19.140 --> 00:38:21.960 but it frees up that time for you to take
00:38:22.033 --> 00:38:24.649 those
00:38:24.650 --> 00:38:26.642 Record it every time.
00:38:26.642 --> 00:38:29.132 So on stuff like that.
00:38:29.140 --> 00:38:30.968 Here, here's my thoughts.
00:38:30.968 --> 00:38:32.339 Come with Kinect.
00:38:32.340 --> 00:38:34.380 I feel this has become really,
00:38:34.380 --> 00:38:36.935 really simple for me where I have,
00:38:36.940 --> 00:38:37.514 you know,
00:38:37.514 --> 00:38:39.810 a little quick powwow with with the devs.
00:38:39.810 --> 00:38:41.175 I know we're going to say no.
00:38:41.180 --> 00:38:43.277 We're going to do I go into that meeting,
00:38:43.280 --> 00:38:45.415 knock it out, jot down my
00:38:45.415 --> 00:38:47.438 and onto the next one right?
00:38:47.440 --> 00:38:49.656 Or on to doing whatever I was doing,
00:38:49.660 --> 00:38:52.138 which is usually just fumbling around
00:38:52.138 --> 00:38:54.613 looking around for like athlete trying
00:38:54.613 --> 00:38:58.024 to solve some dev issues with Seth II.
00:38:58.024 --> 00:38:59.548 Find it super.
00:38:59.550 --> 00:39:01.415 Duper extremely difficult to know
00:39:01.415 --> 00:39:03.750 what I'm going to talk about,
00:39:03.750 --> 00:39:07.074 and especially for lumber,
00:39:07.074 --> 00:39:09.757 considering lumber is like that.
00:39:09.757 --> 00:39:11.452 Back to back every single
00:39:11.452 --> 00:39:12.969 week kind of meeting.
00:39:12.970 --> 00:39:15.058 Luckily right now that has not
00:39:15.058 --> 00:39:16.986 been the case because, you know,
00:39:16.986 --> 00:39:18.862 as CP can can voice we have
00:39:18.862 --> 00:39:20.850 a whole lot to talk about,
00:39:20.850 --> 00:39:24.034 so there's been plenty to talk about now.
00:39:24.040 --> 00:39:26.398 But you know beforehand there was
00:39:26.398 --> 00:39:28.835 even if things were getting done
00:39:28.835 --> 00:39:31.586 ticket wise I could not really see
00:39:31.586 --> 00:39:34.397 those things in the demos and I could
00:39:34.397 --> 00:39:36.008 just voice it right and be like,
00:39:36.008 --> 00:39:37.330 yeah, we did this in this.
00:39:37.330 --> 00:39:38.776 I can't really show you anything.
00:39:38.780 --> 00:39:40.620 I mean we can look through it if you want.
00:39:40.620 --> 00:39:42.559 And yeah I mean the meeting is
00:39:42.559 --> 00:39:44.558 kind of over in 15 minutes in.
00:39:44.560 --> 00:39:48.547 In those cases, what do I jot down really,
00:39:48.550 --> 00:39:50.967 you know like I can,
00:39:50.967 --> 00:39:53.120 I can I always make the agendas for lumber,
00:39:53.120 --> 00:39:54.670 but sometimes there's nothing really.
00:39:54.670 --> 00:39:57.204 Substantial in them in terms of
00:39:57.210 --> 00:39:59.550 Yeah, it is difficult to decide,
00:39:59.550 --> 00:40:01.769 and one of the things I would
00:40:01.769 --> 00:40:03.700 certainly say is even taking
00:40:03.700 --> 00:40:06.640 down that the client is approved
00:40:06.640 --> 00:40:09.548 or the client's fine with it,
00:40:09.548 --> 00:40:10.909 or something's in progress.
00:40:10.909 --> 00:40:13.295 So what I've done in a like at
00:40:13.295 --> 00:40:14.939 least I still have set project,
00:40:14.940 --> 00:40:16.970 I'll just straight up say,
00:40:16.970 --> 00:40:17.534 you know,
00:40:17.534 --> 00:40:18.944 maybe there's a feature working
00:40:18.944 --> 00:40:20.959 on and I'll just say in progress.
00:40:23.210 --> 00:40:25.850 Should be finished by X date or whatever.
00:40:25.850 --> 00:40:28.358 It's just it's helpful to still
00:40:28.358 --> 00:40:30.540 record what you're talking about.
00:40:30.540 --> 00:40:32.542 Because then you can look at your
00:40:32.542 --> 00:40:34.560 32b06fa5-3063-4d06-9ad4-9d679efb5aad
00:40:34.560 --> 00:40:35.600 Oh yeah, that's right.
00:40:35.600 --> 00:40:37.925 We discussed this and it also gives you a
00:40:37.925 --> 00:40:40.080 frame of context like a timeline so to speak,
00:40:40.080 --> 00:40:41.895 of doing what you should
00:40:41.895 --> 00:40:43.347 be talking about next.
00:40:43.350 --> 00:40:45.750 So even just.
00:40:45.750 --> 00:40:48.627 In progress is valid
00:40:48.627 --> 00:40:52.050 all that was discussed where I think
00:40:52.050 --> 00:40:54.895 it gets more difficult to argue that
00:40:54.895 --> 00:40:58.190 is that you run into scenarios where.
00:40:58.190 --> 00:41:00.290 The client will bring up a concern.
00:41:00.290 --> 00:41:02.450 The devil bring up a solution,
00:41:02.450 --> 00:41:04.250 but because nobody recorded
00:41:04.250 --> 00:41:06.950 that meaning like wrote it down,
00:41:06.950 --> 00:41:08.570 you may assume as a PM.
00:41:08.570 --> 00:41:10.285 OK, that's the end of that discussion.
00:41:10.290 --> 00:41:12.562 Like, no, no updates.
00:41:12.562 --> 00:41:14.712 UM, you may actually need to come back
00:41:14.712 --> 00:41:16.745 to that at a later date and check in.
00:41:16.750 --> 00:41:18.550 Oh, what was this solution discussed?
00:41:18.550 --> 00:41:19.526 What was the thing?
00:41:19.526 --> 00:41:22.229 So a lot of that can slide by you if
00:41:22.229 --> 00:41:24.420 you're not trying to take active
00:41:24.420 --> 00:41:26.820 Uh, so even in the shortest of meetings,
00:41:26.820 --> 00:41:28.530 I would recommend trying to
00:41:28.530 --> 00:41:29.556 jot down something.
00:41:29.560 --> 00:41:30.848 At the very least,
00:41:30.848 --> 00:41:32.780 it means that you're paying attention
00:41:32.842 --> 00:41:34.912 and not just hearing the conversation
00:41:34.912 --> 00:41:36.370 like you know you're hearing it,
00:41:36.370 --> 00:41:38.240 but are you actually listening?
00:41:38.240 --> 00:41:40.410 Those can be two very different things.
00:41:40.410 --> 00:41:41.630 But yeah, your
00:41:41.630 --> 00:41:44.486 If your
00:41:44.490 --> 00:41:45.862 I mean that's fine.
00:41:45.862 --> 00:41:47.920 It's not about the length like.
00:41:47.920 --> 00:41:50.179 I I provided this one just because it's like,
00:41:50.180 --> 00:41:50.527 yeah,
00:41:50.527 --> 00:41:52.847 this was a pretty long meeting and
00:41:52.847 --> 00:41:54.743 when we had a lot to talk about,
00:41:54.750 --> 00:41:56.598 but you know some of my meetings is
00:41:56.598 --> 00:41:58.558 just five bullet points and it's like?
00:41:58.560 --> 00:42:00.484 Yep, OK, that's it.
00:42:00.484 --> 00:42:02.889 Cool time to move on.
00:42:02.890 --> 00:42:05.572 And in this kind of brings up another thing,
00:42:05.580 --> 00:42:06.051 uhm.
00:42:06.051 --> 00:42:10.290 Like how do you guys write down
00:42:10.396 --> 00:42:14.288 things or topics you're not exactly a?
00:42:14.290 --> 00:42:16.790 Like really familiar with UM,
00:42:16.790 --> 00:42:19.135 there has been a lot of cases
00:42:19.135 --> 00:42:22.464 where I I hear a dev talking to
00:42:22.464 --> 00:42:24.699 say another clients dev right?
00:42:24.700 --> 00:42:27.220 And to me like I can sort of grasp what's
00:42:27.281 --> 00:42:29.735 happening and what's being talked about,
00:42:29.740 --> 00:42:31.582 but not not well enough that
00:42:31.582 --> 00:42:33.910 by the time I understand it,
00:42:33.910 --> 00:42:36.134 I can write it down because now they're
00:42:36.134 --> 00:42:38.780 on the next topic and so I have been
00:42:38.780 --> 00:42:40.919 solving this issue through transcripts,
00:42:40.920 --> 00:42:43.032 but you guys can already imagine
00:42:43.032 --> 00:42:44.440 Dev speak and transcripts.
00:42:44.440 --> 00:42:48.160 Are basically worthless like.
00:42:48.160 --> 00:42:49.798 And and that, that's a good point.
00:42:49.800 --> 00:42:51.505 I would very strongly encourage
00:42:51.505 --> 00:42:54.100 you not to rely on transcripts.
00:42:54.100 --> 00:42:55.876 The amount of time like if
00:42:55.876 --> 00:42:57.060 you take a transcript,
00:42:57.060 --> 00:42:58.098 just put it in your meeting
00:42:59.060 --> 00:43:00.815 It's probably unreadable.
00:43:00.815 --> 00:43:02.570 Like, broadly speaking,
00:43:02.570 --> 00:43:03.274 like yeah,
00:43:03.274 --> 00:43:05.034 you'll get the main words,
00:43:05.040 --> 00:43:07.679 but like every time you say API,
00:43:07.680 --> 00:43:08.805 it's going to assume you're
00:43:08.805 --> 00:43:09.480 saying something different,
00:43:09.480 --> 00:43:10.608 like you're correct.
00:43:10.608 --> 00:43:13.820 So my advice there is couple of things.
00:43:13.820 --> 00:43:16.997 One is it comes with knowledge base over time
00:43:17.000 --> 00:43:18.008 and a lot of that is.
00:43:18.010 --> 00:43:19.430 I would recommend when you're
00:43:19.430 --> 00:43:20.850 on discovery calls with Kyle,
00:43:20.850 --> 00:43:24.110 he takes amazing technical
00:43:24.110 --> 00:43:27.169 Try and literally just copy what he's
00:43:27.169 --> 00:43:29.225 writing like literally word for word
00:43:29.225 --> 00:43:31.820 what you see him writing down on screen.
00:43:31.820 --> 00:43:33.852 Try and copy that down if you can
00:43:33.852 --> 00:43:35.729 come 'cause he's usually sharing a
00:43:35.729 --> 00:43:37.691 screen when he's taking down
00:43:37.700 --> 00:43:40.610 I found that I do that.
00:43:40.610 --> 00:43:43.706 I stated that meeting
00:43:43.710 --> 00:43:44.850 UM, that was an example.
00:43:44.850 --> 00:43:46.128 There were plenty of times where
00:43:46.128 --> 00:43:47.864 I lost the gist of what was being
00:43:47.864 --> 00:43:49.340 discussed and and did it that way.
00:43:49.340 --> 00:43:50.702 The second thing I would recommend
00:43:50.702 --> 00:43:52.627 is it can be helpful and I did
00:43:52.627 --> 00:43:53.832 this with the cutlery call.
00:43:53.840 --> 00:43:55.772 UM, jump on a quick five minute
00:43:55.772 --> 00:43:57.727 with the dev and say like hey,
00:43:57.730 --> 00:44:00.700 can you confirm what this was?
00:44:00.700 --> 00:44:03.436 Like you know, maybe do that after the call,
00:44:03.440 --> 00:44:06.140 but it can be useful to do that as well.
00:44:06.140 --> 00:44:08.360 The last thing is, again, it's not.
00:44:08.360 --> 00:44:10.520 It's not embarrassing to say hey,
00:44:10.520 --> 00:44:12.160 just want to make sure I record this.
00:44:12.160 --> 00:44:15.364 Did you say this or you know like it'll?
00:44:15.370 --> 00:44:18.058 It'll feel embarrassing to you but
00:44:18.058 --> 00:44:20.199 it's helpful because I'm willing to
00:44:20.199 --> 00:44:22.040 bet you if you didn't understand it.
00:44:22.040 --> 00:44:24.416 There's probably team members on the
00:44:24.420 --> 00:44:26.260 client's side that didn't either.
00:44:26.260 --> 00:44:27.912 And if you're feeling like, oh,
00:44:27.912 --> 00:44:30.180 I'm too embarrassed to ask them to repeat it,
00:44:30.180 --> 00:44:31.416 they are too.
00:44:31.416 --> 00:44:33.888 Which means now you've got multiple,
00:44:33.890 --> 00:44:34.694 you know,
00:44:34.694 --> 00:44:36.704 team members on both parties.
00:44:36.710 --> 00:44:38.410 Who don't understand what was
00:44:38.410 --> 00:44:39.090 being discussed,
00:44:39.090 --> 00:44:41.906 and it's like that's not an ideal scenario.
00:44:41.910 --> 00:44:44.580 So just asking people to repeat
00:44:44.580 --> 00:44:46.890 in non dev speak can be useful
00:44:46.890 --> 00:44:49.610 as well and I do it all the time.
00:44:49.610 --> 00:44:50.044 I don't.
00:44:50.044 --> 00:44:51.346 I don't have any shame anymore,
00:44:51.350 --> 00:44:53.247 but I get that there was shame
00:44:53.250 --> 00:44:55.170 or there's this feeling of like
00:44:55.170 --> 00:44:56.680 I don't really understand it.
00:44:56.680 --> 00:44:59.120 They don't want them to repeat it like.
00:44:59.120 --> 00:45:00.200 If you're feeling that way,
00:45:00.200 --> 00:45:01.215 I guarantee you somebody else
00:45:01.215 --> 00:45:02.430 in the call probably is too.
00:45:06.250 --> 00:45:07.270 Does that answer your question?
00:45:07.270 --> 00:45:10.970 Eric. Yeah no absolutely.
00:45:10.970 --> 00:45:12.458 Where do you guys keep all
00:45:12.458 --> 00:45:13.450 of your meeting
00:45:13.450 --> 00:45:15.641 I know that just having him in
00:45:15.641 --> 00:45:18.141 meeting
00:45:18.141 --> 00:45:20.379 reoccurring meeting is perfect for for
00:45:20.448 --> 00:45:22.778 most meetings that are reoccurring.
00:45:22.780 --> 00:45:25.846 But like one thing I've been thinking
00:45:25.846 --> 00:45:29.145 of trying to get into is putting
00:45:29.145 --> 00:45:31.983 everything into the into the wiki.
00:45:31.990 --> 00:45:33.664 Mainly because I don't want to
00:45:33.664 --> 00:45:35.582 fetch things I want to be able
00:45:35.582 --> 00:45:37.304 to click the client and then just
00:45:37.361 --> 00:45:39.035 find all of the meeting
00:45:39.040 --> 00:45:42.090 Essentially the exact same thing
00:45:42.090 --> 00:45:44.198 that's on the reoccurring meetings.
00:45:44.198 --> 00:45:46.270 But like if I have an internal
00:45:46.330 --> 00:45:47.389 meeting for example,
00:45:47.390 --> 00:45:51.188 it would also be in that same exact area.
00:45:51.190 --> 00:45:53.674 Uhm, I know where that can
00:45:53.674 --> 00:45:55.910 get a little bit like.
00:45:55.910 --> 00:45:56.706 Not fun,
00:45:56.706 --> 00:45:59.492 I think whatever you do is there's
00:45:59.492 --> 00:46:01.850 going to be a negative to it.
00:46:01.850 --> 00:46:04.052 My biggest thing is for Caroline
00:46:04.052 --> 00:46:06.530 and Kelsey who are doing audits.
00:46:06.530 --> 00:46:08.434 They are going to be looking at your
00:46:08.434 --> 00:46:10.009 meeting
00:46:10.010 --> 00:46:13.418 What I find to be very useful is.
00:46:13.420 --> 00:46:15.844 I have all my documents right
00:46:15.844 --> 00:46:17.056 here under SharePoint.
00:46:17.060 --> 00:46:17.828 And it takes me
00:46:19.840 --> 00:46:21.394 123 clicks to find the
00:46:21.394 --> 00:46:23.098 I get where you're coming from.
00:46:23.100 --> 00:46:24.240 And I totally understand that.
00:46:24.240 --> 00:46:25.740 It's like, yeah, that's annoying to
00:46:25.740 --> 00:46:27.916 have to pull up files or and it's
00:46:27.916 --> 00:46:29.596 especially annoying if you're having to
00:46:29.647 --> 00:46:31.537 navigate teams 'cause you can get solid
00:46:31.537 --> 00:46:33.874 seconds of wait times for each click.
00:46:33.874 --> 00:46:37.319 I find that to be useful again though,
00:46:37.320 --> 00:46:39.036 in reoccurring meetings I have them
00:46:39.036 --> 00:46:41.160 in the meeting
00:46:41.160 --> 00:46:44.800 I'm not opposed at all to wikis,
00:46:44.800 --> 00:46:46.392 I just don't think.
00:46:46.392 --> 00:46:48.780 Getting everybody to use the wiki
00:46:48.856 --> 00:46:51.404 that way is going to be effective.
00:46:51.410 --> 00:46:53.363 What I will say to you Eric is if
00:46:53.363 --> 00:46:55.556 you can prove that that's useful and
00:46:55.556 --> 00:46:57.258 that other people are potentially
00:46:57.258 --> 00:46:59.478 able to easily find those
00:46:59.480 --> 00:47:02.266 I'm totally down for switching my process.
00:47:02.270 --> 00:47:04.710 This is the process I was given and
00:47:04.710 --> 00:47:07.240 I found to be useful, but I get it.
00:47:07.240 --> 00:47:08.980 It is annoying to have to like.
00:47:08.980 --> 00:47:11.068 Go through here and click things
00:47:11.068 --> 00:47:13.110 five different times just to pull
00:47:13.110 --> 00:47:16.310 up your old meeting
00:47:16.310 --> 00:47:17.605 I know that's not really a solution
00:47:17.605 --> 00:47:18.599 to what you just said,
00:47:18.600 --> 00:47:20.646 but it's it's more of like.
00:47:20.650 --> 00:47:21.643 I think it's.
00:47:21.643 --> 00:47:23.629 Until we find a better method,
00:47:23.630 --> 00:47:26.906 we have to kind of stick to
00:47:26.906 --> 00:47:29.130 a standard process Miller.
00:47:29.130 --> 00:47:31.110 And you can be absolutely agree.
00:47:31.110 --> 00:47:33.672 You could alternatively be like Caroline
00:47:33.672 --> 00:47:37.208 and put them in a cute little
00:47:37.210 --> 00:47:38.080 Cool
00:47:38.080 --> 00:47:39.820 Actually, what is it?
00:47:39.820 --> 00:47:40.306 That's a cool.
00:47:40.306 --> 00:47:41.440 And why do you have a UPS?
00:47:41.440 --> 00:47:45.190 One 'cause 'cause of my previous project
00:47:45.190 --> 00:47:48.385 our my previous job I used to get swag
00:47:48.385 --> 00:47:50.729 from UPS when we integrated with them.
00:47:50.730 --> 00:47:52.666 It said Caroline was typing for some reason.
00:47:52.670 --> 00:47:54.026 I thought that was from Caroline,
00:47:54.030 --> 00:47:56.088 so that was yeah, that's all me.
00:47:56.090 --> 00:47:57.474 I have a different.
00:47:57.474 --> 00:47:59.550 I have a
00:47:59.633 --> 00:48:00.930 project I was like.
00:48:00.930 --> 00:48:02.490 I don't know why would you
00:48:02.490 --> 00:48:03.890 torture yourself like that?
00:48:03.890 --> 00:48:07.276 'cause I for some weird reason
00:48:07.276 --> 00:48:09.780 cannot physically type well.
00:48:09.780 --> 00:48:11.200 I'm talking to clients,
00:48:11.200 --> 00:48:12.975 it just my I it.
00:48:12.980 --> 00:48:15.725 I don't know why I have that same problem.
00:48:15.730 --> 00:48:17.795 But then I have the problem of
00:48:17.795 --> 00:48:20.007 finding it like my
00:48:20.007 --> 00:48:22.257 I just jot down everything and that
00:48:22.257 --> 00:48:24.593 makes it so much better for my head.
00:48:24.600 --> 00:48:27.560 But then I'm like now I have to put it
00:48:27.560 --> 00:48:31.130 onto the computer which is like great.
00:48:31.130 --> 00:48:33.690 Now that doesn't help.
00:48:33.690 --> 00:48:35.405 Take a screenshot with your
00:48:35.405 --> 00:48:36.777 phone and upload that.
00:48:36.780 --> 00:48:37.172 I know.
00:48:37.172 --> 00:48:38.348 I mean I could do that,
00:48:38.350 --> 00:48:42.404 but my my handwriting is really, really bad.
00:48:42.404 --> 00:48:42.786 Yeah,
00:48:42.786 --> 00:48:45.460 I I surprised I closed my
00:48:48.190 --> 00:48:50.870 Uhm, I would avoid doing what Stephanie does.
00:48:50.870 --> 00:48:52.742 No offence, Stephanie yeah,
00:48:52.742 --> 00:48:54.254 but it's terrible.
00:48:54.254 --> 00:48:58.430 But again, I leave awkward pauses in my
00:48:58.533 --> 00:49:02.109 conversation all the time, like I just.
00:49:02.109 --> 00:49:03.874 It doesn't faze me anymore.
00:49:03.880 --> 00:49:04.970 I have no problems with.
00:49:04.970 --> 00:49:09.458 It's like. Now granted, I am,
00:49:09.460 --> 00:49:11.378 and this is an insult to anybody.
00:49:11.380 --> 00:49:13.627 It's something that has come over time
00:49:13.627 --> 00:49:16.047 as I've gotten better at talking
00:49:16.050 --> 00:49:17.220 I'm a little bit quicker about
00:49:17.220 --> 00:49:18.650 a lot of this stuff, but.
00:49:18.650 --> 00:49:20.630 Like I said, I mean it.
00:49:20.630 --> 00:49:21.734 It comes with time,
00:49:21.734 --> 00:49:23.390 but ultimately you have to be
00:49:23.453 --> 00:49:25.084 doing it to get better at it.
00:49:25.090 --> 00:49:27.820 So UM, my general advice is
00:49:27.820 --> 00:49:32.298 is just try UM and and.
00:49:32.300 --> 00:49:34.582 You know when you reach those points
00:49:34.582 --> 00:49:37.129 where it's like I don't have this
00:49:37.129 --> 00:49:39.148 sentence fully completed and you know
00:49:39.148 --> 00:49:41.220 we're we're at a natural stopping point.
00:49:41.220 --> 00:49:42.576 It's like just tell the client,
00:49:42.580 --> 00:49:43.690 OK, give me one second.
00:49:43.690 --> 00:49:45.104 I'm just going to
00:49:45.110 --> 00:49:48.800 I've never had a client complain like.
00:49:48.800 --> 00:49:52.700 Yeah. That's my general thought process.
00:49:52.700 --> 00:49:53.900 I don't know why I can't type it.
00:49:53.900 --> 00:49:55.112 I do that with my handwritten
00:49:56.100 --> 00:49:58.207 Let me just capture this real quick
00:49:58.207 --> 00:50:00.600 and exactly everybody's fine with it.
00:50:00.600 --> 00:50:04.504 So and I to be fair, I I don't know.
00:50:04.504 --> 00:50:06.391 You know what people's experience was
00:50:06.391 --> 00:50:07.933 in either high school or college,
00:50:07.940 --> 00:50:10.364 but it probably comes a lot from that.
00:50:10.370 --> 00:50:12.899 I know when I was taking
00:50:12.900 --> 00:50:14.760 it was very frustrating when,
00:50:14.760 --> 00:50:15.957 like we just changed to a new
00:50:15.957 --> 00:50:17.081 subject and it's like, well,
00:50:17.081 --> 00:50:19.367 I guess my
00:50:19.370 --> 00:50:19.587 Uhm,
00:50:19.587 --> 00:50:21.106 so there's this rush of like I
00:50:21.106 --> 00:50:22.781 gotta record exactly what people are
00:50:22.781 --> 00:50:24.266 saying exactly when it's happening,
00:50:24.270 --> 00:50:26.142 but it's like I wouldn't really
00:50:26.142 --> 00:50:27.078 worry about transcribing.
00:50:27.080 --> 00:50:29.537 I would more worry about trying to
00:50:29.537 --> 00:50:31.058 understand what the conversation
00:50:31.058 --> 00:50:32.670 is and
00:50:32.670 --> 00:50:35.496 Ideally type while people are talking.
00:50:35.500 --> 00:50:38.010 But if you can't do that, then, uh,
00:50:38.010 --> 00:50:41.633 just try and stop the conversation again.
00:50:41.633 --> 00:50:44.697 Brian Brian Lee and Kyle are both really
00:50:44.697 --> 00:50:47.815 good about like saying well hold on wait.
00:50:47.820 --> 00:50:49.105 Just wanna make sure I've
00:50:49.105 --> 00:50:49.876 got this information.
00:50:53.110 --> 00:50:57.142 Radio yeah, he's freaking gone nuts
00:50:57.142 --> 00:51:01.036 so if there's no other points of
00:51:01.036 --> 00:51:03.986 discussion or nothing. Kevin Brian.
00:51:03.986 --> 00:51:08.289 Do I have anything no where in?
00:51:10.890 --> 00:51:13.270 Lyrics. I'm like you can.
00:51:13.270 --> 00:51:15.377 You can always shoot us a message
00:51:15.377 --> 00:51:17.587 too if you need clarification on
00:51:17.587 --> 00:51:19.955 on stuff for uh before before your
00:51:19.955 --> 00:51:21.500 meetings with clients as well.
00:51:21.500 --> 00:51:25.595 If I or Kyle were sitting on it too.
00:51:25.600 --> 00:51:27.980 Any refresher?
00:51:27.980 --> 00:51:29.905 Yeah, do that on the regular with
00:51:29.905 --> 00:51:31.520 all things Campagna at the moment.
00:51:31.520 --> 00:51:35.008 So till I can get up to speed.
00:51:35.010 --> 00:51:36.186 Brian Lee and Kyle.
00:51:36.186 --> 00:51:38.328 They they do their own internal syncs
00:51:38.328 --> 00:51:40.547 to go over project meetings coming up.
00:51:40.550 --> 00:51:43.022 So if you're a project manager
00:51:43.022 --> 00:51:45.160 and you're not doing that,
00:51:45.160 --> 00:51:48.221 but like the business analyst team is like,
00:51:48.221 --> 00:51:49.847 you know they're doing their job.
00:51:49.850 --> 00:51:51.320 You, you've also got a New Years,
00:51:51.320 --> 00:51:53.180 so you gotta be meeting internally
00:51:53.180 --> 00:51:55.089 and sometimes my when I say like,
00:51:55.090 --> 00:51:56.554 oh, you got to meet with your dev.
00:51:56.560 --> 00:51:59.056 Maybe it's just a simple chat icon times.
00:51:59.056 --> 00:52:00.897 I just ask Eric Weathers hey what's
00:52:00.897 --> 00:52:02.606 the status of these four sinks?
00:52:02.610 --> 00:52:04.864 It gives me one one sentence Parisian.
00:52:04.870 --> 00:52:05.662 It's like cool.
00:52:05.662 --> 00:52:07.800 I know exactly what I must say now.
00:52:07.800 --> 00:52:09.270 It's like it really is as
00:52:09.270 --> 00:52:10.480 simple as you make it.
00:52:10.480 --> 00:52:12.433 It's just you have to be proactive
00:52:12.433 --> 00:52:14.350 and that can be the hard part.
00:52:14.350 --> 00:52:16.058 Is being the proactive side of it.
00:52:18.480 --> 00:52:21.060 So before we break off,
00:52:21.060 --> 00:52:22.915 I kinda wanna get into the habit
00:52:22.915 --> 00:52:24.689 of doing that with SF project,
00:52:24.690 --> 00:52:28.746 but how what's like a good way of
00:52:28.746 --> 00:52:33.436 providing timeline changes for SF project?
00:52:33.436 --> 00:52:36.740 Because maybe a dev doesn't know how
00:52:36.838 --> 00:52:40.108 far like percentage wise we're done.
00:52:40.110 --> 00:52:41.271 For a feature.
00:52:41.271 --> 00:52:44.400 Yeah, and if anybody has to drop off,
00:52:44.400 --> 00:52:45.804 that's totally understandable.
00:52:45.804 --> 00:52:48.612 UM, timelines for Seth were going
00:52:48.612 --> 00:52:51.029 to be difficult when I made
00:52:51.029 --> 00:52:52.804 that Seth Timeline Gantt chart.
00:52:52.804 --> 00:52:55.058 I made it fully knowing you guys
00:52:55.058 --> 00:52:57.651 were going to have to do the heavy
00:52:57.651 --> 00:52:59.486 lifting of figuring out how to
00:52:59.486 --> 00:53:01.364 make it work for your projects.
00:53:01.370 --> 00:53:04.404 Because in my mind it's like, oh Seth,
00:53:04.404 --> 00:53:06.706 you just break it into components and
00:53:06.706 --> 00:53:09.190 then say we're going to work on these five,
00:53:09.190 --> 00:53:10.310 six, eight,
00:53:10.310 --> 00:53:12.788 ten thousand components this Sprint.
00:53:12.788 --> 00:53:13.187 Therefore,
00:53:13.187 --> 00:53:15.182 we're going to keep track
00:53:15.182 --> 00:53:17.100 of that information up.
00:53:17.100 --> 00:53:20.142 It's really easy to talk about
00:53:20.142 --> 00:53:22.170 timelines when I'm talking
00:53:22.267 --> 00:53:24.847 about potentially six things.
00:53:24.850 --> 00:53:26.350 And of those six things,
00:53:26.350 --> 00:53:27.442 only three of them are going
00:53:27.442 --> 00:53:28.708 to be worked on in a Sprint,
00:53:28.710 --> 00:53:31.360 so it's easy for me to do it that way.
00:53:31.360 --> 00:53:31.802 Furseth,
00:53:31.802 --> 00:53:34.012 my recommendation is trying to
00:53:34.012 --> 00:53:36.215 isolate the number of things
00:53:36.215 --> 00:53:38.700 that are being worked on in the
00:53:38.700 --> 00:53:40.463 Sprint and organizing what's
00:53:40.463 --> 00:53:42.898 what's being tracked by that.
00:53:42.900 --> 00:53:45.119 So eliminate how many things are being
00:53:45.119 --> 00:53:47.892 worked on at a time and say like these
00:53:47.892 --> 00:53:50.190 eight things are what we're working on.
00:53:50.190 --> 00:53:51.891 These are the eight things I need
00:53:51.891 --> 00:53:53.558 the client to pay attention to,
00:53:53.560 --> 00:53:56.115 and you know you can kind of,
00:53:56.120 --> 00:53:57.415 I hate to say fudge the numbers,
00:53:57.420 --> 00:53:59.499 but you can make it to where it's like.
00:53:59.500 --> 00:54:01.716 OK, we got 20% in the last Sprint.
00:54:01.720 --> 00:54:02.056 Done,
00:54:02.056 --> 00:54:03.736 but we're really aiming to
00:54:03.736 --> 00:54:05.080 finish everything this Sprint,
00:54:05.080 --> 00:54:06.641 so now it's going to start on
00:54:06.641 --> 00:54:08.119 the start of the Sprint and
00:54:08.119 --> 00:54:09.869 finish at the end of the Sprint.
00:54:09.870 --> 00:54:12.516 Or maybe it finishes after two weeks of QA,
00:54:12.520 --> 00:54:16.039 like you can bake in time for the timeline,
00:54:16.040 --> 00:54:17.144 but you really just.
00:54:17.144 --> 00:54:18.800 It is a case of planning.
00:54:18.800 --> 00:54:21.215 What do you want to be completed
00:54:21.215 --> 00:54:23.460 by the end of the Sprint?
00:54:23.460 --> 00:54:25.000 In my time in Seth,
00:54:25.000 --> 00:54:27.183 it was a lot of like throwing
00:54:27.183 --> 00:54:29.601 as much throwing as many darts
00:54:29.601 --> 00:54:31.739 at the board as I could.
00:54:31.740 --> 00:54:34.548 Uhm, and then seeing what sticks.
00:54:34.550 --> 00:54:37.025 But I think reining it in and saying OK,
00:54:37.030 --> 00:54:39.046 we're going to work on these
00:54:39.046 --> 00:54:40.390 things and everything else,
00:54:40.390 --> 00:54:42.770 even if the client wants us to focus on it,
00:54:42.770 --> 00:54:44.975 they have to take a back seat,
00:54:44.980 --> 00:54:46.884 which is very, very difficult to do.
00:54:46.890 --> 00:54:50.817 And 1000%. I leave that up to.
00:54:50.820 --> 00:54:51.190 Uh,
00:54:51.190 --> 00:54:53.410 people who are dealing with it
00:54:53.410 --> 00:54:56.010 more so to to answer for UM,
00:54:56.010 --> 00:54:59.200 or maybe provide some insight, but.
00:54:59.200 --> 00:55:01.080 Yeah, broad auto broad level.
00:55:01.080 --> 00:55:02.977 I would say for a timeline it's
00:55:02.977 --> 00:55:04.959 better to just try and delineate what
00:55:04.959 --> 00:55:07.270 it is you expect to have completed,
00:55:07.270 --> 00:55:08.726 by what date and you have to work
00:55:08.726 --> 00:55:10.178 with the developers to know that.
00:55:10.180 --> 00:55:10.486 Like,
00:55:10.486 --> 00:55:12.016 is it reasonable to finish
00:55:12.016 --> 00:55:13.240 this feature within this
00:55:13.294 --> 00:55:13.670 spread?
00:55:18.750 --> 00:55:21.900 OK, yeah, I think I I think I really
00:55:21.900 --> 00:55:24.600 just need to force myself to get
00:55:24.600 --> 00:55:26.525 into the habit of doing it because
00:55:26.525 --> 00:55:28.929 it really is a once you don't do it,
00:55:28.930 --> 00:55:30.700 you get really used to it.
00:55:30.700 --> 00:55:33.988 Yeah, and yeah, because I know the value
00:55:33.988 --> 00:55:36.709 because with with lumber and with all
00:55:36.709 --> 00:55:39.419 the all of the connect projects though
00:55:39.419 --> 00:55:43.358 I don't do those that well either.
00:55:43.360 --> 00:55:45.872 Mainly because I just can't take good
00:55:45.872 --> 00:55:48.840 like I need to really figure that part out.
00:55:48.840 --> 00:55:50.304 Not just like a.
00:55:50.304 --> 00:55:51.768 You know doing them,
00:55:51.770 --> 00:55:56.280 but rather doing them well, uhm?
00:55:56.280 --> 00:55:58.308 I know the value in him.
00:55:58.310 --> 00:56:00.398 And I know that the projects that I don't
00:56:00.398 --> 00:56:02.802 do them in tend to be the ones that I have.
00:56:02.810 --> 00:56:04.870 Only like the least amount
00:56:04.870 --> 00:56:06.833 of actual knowledge on like,
00:56:06.833 --> 00:56:09.650 but it really just comes down to like the
00:56:09.716 --> 00:56:12.380 back to back meetings were like kill me.
00:56:12.380 --> 00:56:14.860 The the back to back is the hardest
00:56:14.860 --> 00:56:17.897 part and being able to tell people no on
00:56:17.897 --> 00:56:20.833 those is is where I've gotten more organized.
00:56:20.840 --> 00:56:22.667 Baking time in here and the other
00:56:22.667 --> 00:56:24.803 thing is you can also schedule time
00:56:24.803 --> 00:56:26.741 into your calendar for focused on,
00:56:26.750 --> 00:56:29.880 so that could potentially help you, but.
00:56:29.880 --> 00:56:32.208 What I would certainly say is,
00:56:32.210 --> 00:56:33.538 uh, you can also,
00:56:33.538 --> 00:56:35.530 and I'm going to say this
00:56:35.610 --> 00:56:37.310 is not an alternative.
00:56:37.310 --> 00:56:39.116 It has to be done simultaneously,
00:56:39.116 --> 00:56:40.660 at least starting off.
00:56:40.660 --> 00:56:42.010 But there are plenty of meetings.
00:56:42.010 --> 00:56:44.348 Eric, you sat on these where my
00:56:46.870 --> 00:56:48.984 So especially once we get to UAT,
00:56:48.990 --> 00:56:50.670 I'll be writing down what's the
00:56:50.670 --> 00:56:51.790 issue that they're describing?
00:56:51.790 --> 00:56:53.500 What's the description?
00:56:53.500 --> 00:56:55.210 What's the nodes?
00:56:55.210 --> 00:56:56.765 There are alternative ways that
00:56:56.765 --> 00:56:59.090 you can keep track of information.
00:56:59.090 --> 00:56:59.463 Theoretically,
00:56:59.463 --> 00:57:02.074 you know once you're out of discovery,
00:57:02.080 --> 00:57:03.850 you could potentially just have
00:57:03.850 --> 00:57:05.620 everything being managed in a
00:57:05.684 --> 00:57:07.658 Gantt chart with no leading
00:57:07.660 --> 00:57:09.160 There's downsides to that though,
00:57:09.160 --> 00:57:11.344 where if you get into a heavy discussion
00:57:11.344 --> 00:57:13.239 on how something should work,
00:57:13.240 --> 00:57:15.592 you're not recording that it's it's
00:57:15.592 --> 00:57:18.710 not going to be useful information.
00:57:18.710 --> 00:57:20.470 So I don't know I I don't know
00:57:20.470 --> 00:57:22.108 how helpful that is to you, but.
00:57:22.108 --> 00:57:25.999 It is a case of just the more you do it.
00:57:26.000 --> 00:57:29.006 The the better it will be.
00:57:29.010 --> 00:57:30.036 Yeah, no, definitely.
00:57:30.036 --> 00:57:32.989 It's it really is gonna come down to that.
00:57:32.990 --> 00:57:34.430 UM and hopefully once things
00:57:34.430 --> 00:57:36.130 start slowing down a little bit,
00:57:36.130 --> 00:57:38.580 I'm sure I'll be able to just
00:57:38.580 --> 00:57:40.660 properly like keep track of all
00:57:40.660 --> 00:57:43.568 of this stuff to do and make sure
00:57:43.568 --> 00:57:46.109 that I don't just let it slip.
00:57:46.110 --> 00:57:47.049 Yeah for sure.