Voice to Text for Height
Height is built for teams who care about how they work. But writing task descriptions, comments, and project documentation takes time away from actual execution. Every well-written task means minutes not spent building. Blurt lets you hold a button, speak naturally, and release. Your text appears instantly in any Height text field. Task descriptions, comments, project documents, status updates. No copying, no pasting, no switching apps. Just talk and execute.
The Typing Problem
Writing detailed task descriptions slows down your workflow
You know exactly what needs to be done. You could explain it in thirty seconds. But typing out the context, requirements, and edge cases takes ten minutes. So you write a brief title and hope the assignee understands. They don't. A Slack thread follows. You explain it verbally anyway. The time you saved typing is gone.
Comments that should add context become one-liners
You're reviewing a task. There's important context about what you've tried, why a certain approach won't work, and what the next steps should be. Typing all that takes five minutes. So you write 'checked this, needs more investigation' and move on. The next person picking up this task has to rediscover everything you already know.
Project documents never get the depth they need
A new project needs background, goals, scope, and constraints. You have all of this in your head from the last three discussions. But writing a proper document means blocking off an hour. You write the minimum version. The team starts without full context. Questions follow. Alignment takes longer than documenting would have.
Status updates slip because writing takes too long
Your team lead wants weekly updates. Stakeholders want visibility. You know exactly where things stand, but nobody has time to write reports. Updates slip. A week becomes two. Suddenly you're fielding questions that a simple status update would have answered. Not writing costs more than writing, but typing still takes too long.
Feedback on tasks becomes superficial
You're triaging tasks or reviewing someone's work. Thoughtful feedback requires paragraphs. Explaining why an approach is problematic, suggesting alternatives, sharing relevant context. Typing all that for every task is exhausting. So you leave brief comments that don't fully communicate what you know. Quality suffers.
How It Works
Blurt works everywhere in Height: tasks, projects, lists, comments, and documents. Anywhere you can type, you can talk.
Click into any Height text field
Put your cursor in a task description, comment, project document, or any text area in Height.
Hold your hotkey and speak
Press your chosen shortcut and talk naturally. Describe the task, explain the context, list the requirements. Blurt adds punctuation automatically.
Release and keep executing
Your text appears at the cursor. Move to the next task, the next project, the next update. Documentation done, back to building.
Real Scenarios
Writing task descriptions with complete context
You just identified a bug in the notification system. Hold the button and describe it: 'When a user has more than ten notification preferences enabled, the settings page takes over four seconds to load. Initial investigation shows the API is making individual database queries for each preference instead of batching them. This affects roughly fifteen percent of power users based on our analytics. Acceptance criteria: settings page loads in under one second regardless of preference count. The fix should batch all preference queries into a single database call.' Task created with full context in forty seconds. Whoever picks it up knows exactly what to do.
Adding detailed comments during task review
You're going through your team's tasks. Each needs feedback. Hold the button: 'I looked at this approach and it won't work because the third-party API has rate limits we'd hit within minutes. Instead, we should implement a queue system that processes requests in batches. I've seen this pattern work well in the payments service. Happy to pair on the implementation if helpful.' Meaningful feedback in fifteen seconds instead of five minutes of typing.
Capturing decisions in project documents
Your team just finished a discussion about technical architecture. Before details fade, hold the button and dictate: 'We decided to use PostgreSQL instead of MongoDB for the analytics service. Primary reasons: complex queries across multiple tables are central to the feature, and the team has more PostgreSQL experience. We considered MongoDB for its flexibility but the query patterns don't fit a document model. Migration path: start fresh with PostgreSQL, no need to migrate existing data.' Decision documented while it's still fresh.
Quick status updates across multiple tasks
End of day. You need to update several tasks with progress. Hold the button on each: 'Made good progress today. Completed the database schema changes and the API endpoints. Still need to wire up the frontend and write tests. Estimate two more days to completion.' Next task: 'Blocked on design review. Pinged the design team in Slack, waiting for response. Will update once I hear back.' Next: 'Done. Merged and deployed to staging. Ready for QA when they have capacity.' Five updates in two minutes.
Creating comprehensive project briefs
A new initiative needs a project document. Hold and dictate: 'Project goal: reduce customer churn by improving the onboarding experience. Background: analytics show forty percent of new users don't complete onboarding, and those who don't complete it have three times higher churn. Scope: redesign the first-run experience, add progress indicators, and implement smart defaults based on user type. Out of scope: changes to pricing or the core product. Success metrics: onboarding completion rate above seventy-five percent, thirty-day retention improvement of ten percentage points.' Project brief created in ninety seconds.
Documenting blockers and dependencies
You're stuck waiting on another team. Document it properly. Hold the button: 'Blocked on infrastructure team to provision the new staging environment. I've requested this via their intake process, ticket number 4521. Expected turnaround is three business days. Once we have the environment, we can begin integration testing. No further progress possible on this task until then. Risk: if provisioning takes longer than expected, we'll miss the end-of-sprint deadline.' Clear blocker documentation that helps everyone understand the situation.
Rapid task creation during brainstorming
Your team is brainstorming features. Ideas are flying. Capture them in Height as they come. Hold: 'Add ability to export reports to PDF format. Users have requested this for sharing with stakeholders who don't have Height access.' Next: 'Implement keyboard shortcuts for common actions. Power users are asking for ways to navigate without touching the mouse.' Next: 'Consider dark mode support. Multiple requests in feedback channel.' Ideas captured at the speed of conversation.
Why Height users choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Double-tap function key or click microphone |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical terms | Handles project management vocabulary well | Often mishears technical terms |
| Consistency | Reliable in Height's web and desktop apps | Sometimes fails in web-based text fields |
| Pricing | $10/month or $99/year, free tier included | Free but limited accuracy |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt