Logo
    Search

    project_management

    Explore "project_management" with insightful episodes like "Ep. 294: A Tactical Assault on Busyness", "Potluck - Working on a Team × Dealing with Imposter Syndrome × Animating on the Web × Icon Libraries × Demanding Clients", "The Freelance Client Lifecycle - Part 2" and "Dropping "Aspirations"... DO THE WORK #508" from podcasts like ""Deep Questions with Cal Newport", "Syntax - Tasty Web Development Treats", "Syntax - Tasty Web Development Treats" and "Do The Work"" and more!

    Episodes (4)

    Ep. 294: A Tactical Assault on Busyness

    Ep. 294: A Tactical Assault on Busyness

    One of the biggest problems afflicting knowledge workers in the digital age is frantic busyness; days filled with emails, chats, and meetings, without much to show for all the effort. In today’s episode, Cal dives into one of the most-discussed ideas from his new book, Slow Productivity, which offers a simple, tactical assault on this state of persistent busyness. He then answers listener questions about similar issues and lists the book he read in March.

    Below are the questions covered in today's episode (with their timestamps). Get your questions answered by Cal! Here’s the link: bit.ly/3U3sTvo

    Video from today’s episode:  hyoutube.com/calnewportmedia

    Deep Dive: A Tactical Assault on Busyness [3:47]

    - How can I stop chasing the “perfect” productivity system? [34:51]
    - How do I avoid losing my day to distraction? [39:08] 
    - How do I help my partner escape meeting quickstand? [42:31]
    - How do we design the perfect client/task/scheduling system? [48:59]
    - Can Apple Vision Pro help deep work? [54:46]

    The 5 Books Cal Read in March 2024 [1:06:43]

    A Short History of England (Simon Jenkins)
    Into the Impossible (Brian Keating)
    The Amen Effect (Sharon Brous)
    Sink the Bismark! (CS Forester)
    Hidden Potential (Adam Grant)

    Links:
    Buy Cal’s latest book, “Slow Productivity” at calnewport.com/slow
    newyorker.com/science/annals-of-artificial-intelligence/can-an-ai-make-plans
    Thanks to our Sponsors:

    This episode is sponsored by BetterHelp. Give online therapy a try at betterhelp.com/deepquestions
    expressvpn.com/deep
    zocdoc.com/deep
    notion.com/cal

    Thanks to Jesse Miller for production, Jay Kerstens for the intro music, Kieron Rees for slow productivity music, and Mark Miles for mastering.

    Potluck - Working on a Team × Dealing with Imposter Syndrome × Animating on the Web × Icon Libraries × Demanding Clients

    Potluck - Working on a Team × Dealing with Imposter Syndrome × Animating on the Web × Icon Libraries × Demanding Clients

    In this potluck episode of Syntax, Wes and Scott answer your questions about working on a team, dealing with imposter syndrome, animating on the web, using the table element, landing pages for apps, and building full stack apps with NextJS.

    Sentry - Sponsor

    If you want to know what’s happening with your code, track errors and monitor performance with Sentry. Sentry’s Application Monitoring platform helps developers see performance issues, fix errors faster, and optimize their code health. Cut your time on error resolution from hours to minutes. It works with any language and integrates with dozens of other services. Syntax listeners new to Sentry can get two months for free by visiting Sentry.io and using the coupon code TASTYTREAT during sign up.

    Sanity - Sponsor

    Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get a Sanity powered site up and running in minutes at sanity.io/create. Get an awesome supercharged free developer plan on sanity.io/syntax.

    Freshbooks - Sponsor

    Get a 30 day free trial of Freshbooks at freshbooks.com/syntax.

    Show Notes

    ××× SIIIIICK ××× PIIIICKS ×××

    Shameless Plugs

    Tweet us your tasty treats

    The Freelance Client Lifecycle - Part 2

    The Freelance Client Lifecycle - Part 2

    In this episode Scott and Wes continue their discussion about the freelance client lifecycle—from design and development, to project hand-off, and everything in between.

    Sanity.io - Sponsor

    Sanity.io is a real-time headless CMS with a fully customizable Content Studio built in React. Get up and running by typing npm i -g @sanity/cli && sanity init in your command line. Get an awesome supercharged free developer plan on sanity.io/syntax.

    Freshbooks - Sponsor

    Get a 30 day free trial of Freshbooks at freshbooks.com/syntax and put SYNTAX in the “How did you hear about us?” section.

    Show Notes

    1:47 - Design

    • Collect all assets from your client
      • Logo
      • Brand guidelines
      • List of likes and dislikes
    • Create initial look and feel
    • Don’t show client too early—they can be distracted by little unfinished things
    • Back up the “whys” of what you did. Otherwise, it’s just a pretty picture and and the client only thinks about it in terms of taste. Remember, you are the expert they hired, so it’s not totally subjective—you have the expertise and you need to flex that.
      • This button is teal because it’s your call to action—this is the button that makes you money so we want to highlight that
      • Grey text on white background is hard to read—you’ll be leaving people out if you do this.
      • When possible, draw circles or golden ratio lines around everything ;)
    • Be prepared for non-standard feedback
      • E.g. this feels cloudy, can it look more sunny? Please make it pop, etc.
    • Don’t get offended by feedback on creative work
      • Clients didn’t go to art school and don’t know about good feedback.
      • Clients will ignore all finished aspects of a design and only focus on the one minor thing that’s incorrect.
    • Revisions

    17:58 - Development

    • Clear requirements make development much easier.
    • Sometimes this starts at the same time or in the process of design.
    • Only show dev progress if client is capable of understanding dev process.
      • Showing a developed site too early can cause clients to worry about visual aspects that aren’t yet in line with the design.
      • Showing to early is also a recipe for a feedback list of things you already know.
    • Give regular progress updates, as previously established. Make it happen on a schedule so expectations are set and so you won’t forget. Stick to your timeline!
    • Clients don’t care about technical jargon.
      • Don’t tell clients about Gatsby/React as much as telling them about the benefits, how fast the site is, etc.

    23:48 - Feedback and revisions

    • Feedback is done in revisions or rounds.
    • For smaller projects, have your client email (one email) a list of feedback.
    • For larger projects, and more technical clients, use bug tracking software, such as Github issues, Trello, etc.
    • Write down everything, and then have a follow-up call to discuss the feedback.

    30:08 - Deployment

    • Get your client to pay for domains and hosting.
    • Make sure their old website has everything off of it, or host the website somewhere else.
    • If you’re moving servers, best to just point the A records at the new server.
    • If changing nameservers for DNS, make sure the client doesn’t have email or any other apps on that server that will be nuked or broken when moving.
    • Many clients use their server to uploaded PDFs and other files that may still need to be accessible.
    • If you are changing URL structure, you’ll need to be aware of any redirects.
    • Backup strategies
    • Restoration strategies

    40:05 - Handoff

    • Create a video detailing how to do each thing
    • Don’t give more options than they need in the back end.
    • Do in-person training when possible.
      • Only teach them the things that are important for their day to day usage.

    44:28 - Bug fixes and support

    • Very common for clients with wrong idea of project guidelines to want to add on at the end of a project.
    • Not about adding new, non-established features.
    • Emergency bugs require an emergency response if they are your fault
      • Set expectations and be careful what you promise.

    48:03 - What to do when things go to shit

    • There should be a trail of communication leading up to things going awry.
    • Project is behind.
    • Product is not met with acceptance.
    • Client isn’t paying.
    • When to fire your client.

    Links

    ××× SIIIIICK ××× PIIIICKS ×××

    Shameless Plugs

    Tweet us your tasty treats!

    Dropping "Aspirations"... DO THE WORK #508

    Dropping "Aspirations"... DO THE WORK #508

    DO THE WORK PODCAST:

    A dailyish documentary of my life blending together fatherhood, business, organization, and life hacking to make it all work.  

     

    Produced by podcaster, entrepreneur and dad of three daughters - Diego Footer.

     

    My Podcasts:

    Farm Small, Farm Smart: http://bit.ly/2vMUDvX

    Grass Fed Life: http://bit.ly/2uOsLTH

    Voices of Change: http://bit.ly/2vrn81r

     

    My Audiobooks:

    The Market Gardener by JM Fortier: http://bit.ly/2uynxvU

    The Urban Farmer by Curtis Stone:  http://bit.ly/2uynxvU

     

    My Business:

    Paperpot Transplanter: http://www.paperpot.co

     

    Support content I have created:

    http://www.permaculturevoices.com/support

     

    Support while you shop at Amazon:

    http://amzn.to/2yu1zPj