How to Create a Project Dashboard in Looker
Creating a project dashboard in Looker is one of the best ways to get everyone on the same page, turning complex data from spreadsheets and project management tools into a clear, visual story of your progress. This guide will walk you through the essential steps, from planning your layout to building insightful visualizations that keep your projects running smoothly.
Why Build a Project Dashboard in Looker?
Before jumping into the builder, it helps to know why you're doing this. A purpose-built project dashboard in Looker centralizes all your key information, replacing the need to dig through different tools and reports. Instead of static data in exported CSVs, you get a live, interactive view of project health. This allows you to spot bottlenecks, manage resources, and communicate progress to stakeholders with confidence, all from one place.
Before You Build: Planning Your Dashboard
A great dashboard starts with a great plan, not with clicking around in the tool. Taking ten minutes to plan will save you hours of rebuilding later.
1. Define Your Key Questions and Metrics (KPIs)
First, figure out what questions your dashboard needs to answer. Your goal is to move from raw data to actionable insights. Common project management questions include:
- What is the overall progress of the project?
- Are we on schedule and within budget?
- Which tasks are overdue or creating bottlenecks?
- What is the workload distribution across the team?
- How many issues or bugs are open versus resolved?
These questions help you identify your key performance indicators (KPIs). For a project dashboard, your KPIs might be:
- Task Completion Rate: (Completed Tasks / Total Tasks) x 100
- Budget vs. Actuals: The amount spent compared to the amount allocated.
- Cycle Time: The average time it takes to complete a task.
- Team Velocity: The number of tasks or story points a team completes in a set period.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
2. Identify Your Data Source(s)
Where does your project data live? Usually, it's in a project management tool like Jira, Asana, Monday.com, or even a detailed Google Sheet or Excel file. To use this data in Looker, it needs to be accessible in a connected database (like BigQuery, Redshift, or Snowflake). Typically, this step involves a data engineer or analyst who ensures your project data is flowing into a database that Looker can access.
3. Sketch a Simple Layout
You don't need fancy design software. Grab a pen and paper or a whiteboard and sketch out a basic layout. Put the most important, high-level numbers at the top. Think of a newspaper: the main headline is at the top for a reason. Your KPIs like "Overall Progress" or "Budget Spent" should go there.
From there, organize related charts together. For instance, you might have a section for task-related metrics and another for budget and resource metrics. This simple mapping exercise will make the building process much faster.
Step-by-Step Guide to Creating Your Looker Project Dashboard
With your plan in place, you're ready to start building. The process in Looker centers around creating individual visualizations (called "Looks") and then arranging them on a dashboard.
Step 1: Get Familiar with Your Looker Explore
The journey to any visualization in Looker begins in an "Explore." An Explore is a curated starting point created by your data team that lets you query a specific set of data. It's designed to make data accessible without you needing to know SQL.
Your data team will have already set up a LookML model - the code layer that defines your data's business logic. This is a key difference between Looker and other BI tools, it requires this modeling layer upfront. Your job is to find the Explore that contains your project data. It might be named something like "Project Management," "Jira Data," or "Task Analytics."
Step 2: Build Your First Visualization (a "Look")
Let's create a simple bar chart to see how many tasks are assigned to each team member. This is a great way to monitor workload distribution.
- Navigate to Your Explore: Once you've opened the right Explore, you'll see a panel on the left with all available data points.
- Select a Dimension: Dimensions are the "what" fields in your data—they describe things. Scroll through the available dimensions and find one called "Assignee Name" or "Team Member." Click on it to add it to your query.
- Select a Measure: Measures are the "how much" fields—they are numerical values you can count, sum, or average. Find a measure like "Task Count" and click on it.
- Run the Query: Click the Run button. Looker will generate a table with a list of team members and the number of tasks assigned to each.
You have your data, now let’s visualize it.
- Click the Visualization tab. Looker will often intelligently guess the best chart type, but you can select your own.
- Choose the Bar Chart option.
- Use the Settings (gear icon) menu within the Visualization tab to customize labels, colors, and titles to make the chart easy to read.
Step 3: Choose the Right Visualization for Each Metric
To build an effective dashboard, you need more than just one bar chart. Match the visualization type to the insight you’re trying to share.
For Key Performance Indicators (KPIs)
For high-level numbers like "Total Open Tasks" or "Project Budget Remaining," use a Single Value visualization. This displays a single, large number that's easy to see at a glance—perfect for the top of your dashboard.
How to build: Select a single measure (e.g., Task Count) and filter it (e.g., Status = "Open").
For Progress Over Time
To track metrics like tasks completed per week or budget spent over the course of the project, a Line Chart or an Area Chart works best. It visualizes trends clearly.
How to build: Select a date dimension (e.g., "Completion Date" grouped by week) and a measure (e.g., "Task Count").
For Showing Proportions
If you want to show the breakdown of tasks by status (e.g., To Do, In Progress, Complete), a Pie Chart or a Donut Chart can be effective. A quick word of caution: these charts work best with just a few categories. If you have more than five, a bar chart is often easier to interpret.
How to build: Select a dimension with a few categories (e.g., "Task Status") and a measure (e.g., "Task Count").
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
Step 4: Save Your Visualizations to a Dashboard
Once you’ve created a "Look" you're happy with, it's time to add it to your dashboard.
- Click the Gear Icon in the top right of your Look.
- Select Save to Dashboard.
- A dialog box will appear. You can add your visualization to an existing dashboard or create a new one. Let's create a new one called "Quarterly Project Review Dashboard."
- Give your visualization a clear title, like "Tasks per Team Member."
- Click Save to Dashboard.
Repeat this process for all the visualizations you planned, creating individual Looks for budget tracking, timeline progress, task status, etc., and saving each one to your new dashboard.
Step 5: Arrange Your Dashboard and Add Filters
Now, head to your newly created dashboard to arrange your Looks logically and add interactive elements.
- Arrange Tiles: You can drag, drop, and resize each Look (called a "tile" on the dashboard) to match the layout you sketched out. Put your high-level KPIs at the top and group related charts.
- Add Dashboard Filters: Filters are what make a dashboard truly powerful and interactive. You can add a dashboard-level filter that applies to multiple charts at once. Common filters for a project dashboard include:
To add a filter, click Add Filter from the dashboard menu, select the field you want to filter by, and then configure which tiles the filter should apply to.
Best Practices for an Effective Project Dashboard
Building the dashboard is just one step. Making it effective is what matters most. Here are a few final tips:
- Start with the Summary: Assume your audience only has 30 seconds. Put the most critical information at the top so they can get the main takeaways instantly.
- Keep It Simple: Avoid cluttering your dashboard with too much information. If a visualization isn't answering a key question from your plan, it probably doesn't belong.
- Use Clear Titles: Write descriptive titles for each chart. Instead of "Task Count by Date," use "New Tasks Created Per Week." Tell the story of what the chart represents.
- Schedule and Share: Use Looker's scheduling feature to automatically send a PDF or an email of the dashboard to stakeholders every Monday morning. This keeps everyone informed and makes reporting effortless.
Final Thoughts
Building a project dashboard in Looker involves a structured process of planning, data exploration, and visualization. While the initial setup with LookML data models requires technical groundwork, the result is a robust, single source of truth that empowers you and your team to make data-informed decisions and keep projects on track.
If that process of developing data models and learning a complex BI tool like Looker feels like a bit much just to see your project metrics, it's worth exploring alternatives. We built Graphed to remove that friction. Instead of needing a data engineer to set up models, you can connect your data sources in a few clicks. And instead of wrestling with chart builders, you just describe the dashboard you want in plain English, and our AI analyst creates it for you in seconds, providing a live and interactive view of your business performance without the steep learning curve.
Related Articles
How to Create Facebook Ads API for Claude Code
Create a Meta Marketing API access token that never expires, using a system user, so Claude Code can pull Facebook ad reports and manage campaigns.
ClickHouse vs Postgres: When to Switch to Columnar
Comparing ClickHouse vs PostgreSQL means matching storage architecture to workload. Row storage wins for transactions. Columnar wins for scan-heavy analytics.
Google Ads for Orthodontists: Get More Booked Consults
Most orthodontic Google Ads campaigns waste money on low-intent searches. The problem is structure, not the platform.