// description
A horizontal bar chart that visualises a project schedule — tasks on the vertical axis, time on the horizontal axis, with bars showing the start date, duration, and end date of each task. Dependencies between tasks (Task B can't start until Task A is done) can be shown with connecting arrows.
// history
Henry Gantt, an American mechanical engineer and management consultant, developed the Gantt chart in the 1910s while working with Frederick Winslow Taylor on scientific management. It was first used for major U.S. government construction and infrastructure projects. Gantt charts were largely hand-drawn until the 1980s, when project management software made them accessible. They remain one of the most widely used project planning tools in construction, engineering, and software development.
// example
Planning a 6-week course launch: Week 1-2 — record all video lessons. Week 2-3 — edit videos (starts when first recordings are done). Week 3 — build sales page (can run parallel to editing). Week 4 — set up email sequence. Week 5 — beta test with 5 students. Week 6 — fix based on feedback, open public enrolment. A Gantt chart makes the overlaps, dependencies, and critical path visible at a glance.
// katharyne's take
For complex launches, I absolutely use a Gantt-style timeline — even if it's just a table in Notion. The thing it does that no other tool does as well is show you the dependencies: what can't start until something else is done. That's where projects get stuck. You can't write the sales page until you know what's in the course. You can't open enrolment until the payment system is tested. Map those dependencies and your timeline becomes realistic, not optimistic.
// creative uses
- Use a Gantt table in Notion to plan a KDP series launch: map out the illustration phase, formatting, cover design, keyword research, and listing creation as separate rows with date ranges. You'll immediately see that keyword research needs to happen before you write the listing — not after — and that cover design can run parallel to interior formatting.
- Apply a lightweight Gantt to your quarterly content plan: put your content pillars on the vertical axis and weeks on the horizontal. Map when each batch of posts, emails, or videos is created vs. scheduled vs. published. You'll spot gaps before they happen rather than scrambling mid-week.
- When launching a digital product on Etsy + Gumroad simultaneously, use a simple Gantt table to coordinate the parallel tracks: Etsy listing, Gumroad product page, email announcement, social posts, and Pinterest pins. Dependencies become obvious — you need the product file done before you can create mockups, and mockups before you can write Etsy copy.
// quick actions
- Open Notion (or a plain spreadsheet) and create a 5-column table: Task | Start | End | Depends On | Status. Fill it in for your current project. You now have a functional Gantt. Do this before you do anything else on the project today.
- Look at your current project plan (even if it's in your head) and identify the single task that blocks the most other tasks. That's your critical path item. Schedule it first and protect its time — everything downstream is waiting on it.
- If you have a launch coming up in the next 4 weeks, work backwards from the launch date and map every task with its duration. If the total time required exceeds 4 weeks of available hours, you need to cut scope (MoSCoW) or push the date. Do this calculation today before you're two weeks in and already behind.
// prompt ideas
Help me build a Gantt-style launch plan for my upcoming [KDP book / Etsy product / digital course] launch. My target launch date is [date]. List every task involved in the launch, estimate a realistic duration for each, identify the dependencies between tasks, and tell me what the critical path is — the sequence I absolutely cannot afford to delay.
I'm trying to run [number] of business streams simultaneously: [list them — e.g. KDP publishing, Etsy shop, email list, course creation]. Create a simplified weekly Gantt table for the next 4 weeks that allocates realistic time blocks to each stream based on [X hours per week] of available creative work time. Flag any weeks where conflicts or bottlenecks are likely.
I have a [product launch / course release / shop overhaul] I need to complete in [X weeks] but I'm not sure if that's realistic. Here are all the tasks I know about: [list them]. Build a Gantt chart, identify the total time required assuming [X hours/week], and tell me honestly whether the timeline is achievable or what I need to cut or outsource to make it work.