Lyyli
Project management tells you what to do. Lyyli also keeps track of what to say.
A task like "draft a press release" does not yet say who the audience is, what the core message is, who comments, who approves or which version is latest. Lyyli keeps communications context with the content from planning to approval, so the team does not rebuild the whole picture at every step.
How is Lyyli different from generic project management?
Lyyli complements general project management with communications-built context and workflow. Asana, Jira and Planner manage tasks well, but they do not keep channel versions, comment rounds or approval together. Lyyli connects projects, tasks, content cards and approval to communications objects.
Who this is for
Communications teams and directors running campaigns, internal programmes or multichannel content sets. Especially relevant on Professional, where assignees and organisation management are included.
How a communications project moves
- 1
Create a project or campaign and define the goal
- 2
Create communications tasks and channel versions from the plan, chat or approved meeting proposals
- 3
Track work in Kanban or calendar with owners
- 4
Keep drafts, comments and versions on the same card
- 5
Approve and take finished content to your organisation's existing publishing channels
Benefits for leadership
You see communications project status without a separate status meeting for every thread. Professional adds workload overview, approvals and audit trail in the same view.
Typical use cases
Campaign as content cards
A campaign is not only a task list. Each channel version lives on a card with owner, deadline and comments.
Internal programme in Kanban
See what waits for a draft, what waits for review and what is ready to take out. Calendar shows deadlines.
Difference from a general PM tool
Jira or Asana does not know an approval round or a channel version. Lyyli keeps communications context on the card.
General project management vs. Lyyli
Lyyli does not replace every project tool. It is built for communications work objects.
| General PM tool | Lyyli | |
|---|---|---|
| Object | Ticket or task | Content card and channel versions |
| Approval | Custom field or attachment | Process on the card on Professional |
| Context | No brand voice | Organisational context in drafting |
| Publishing | No communications process | Approve in Lyyli, take to destination |
FAQ
- Does Lyyli replace Jira or Asana?
- Not for everything. Lyyli is built for communications objects and complements general project management. It does not replace engineering or IT project management.
- How does approval relate to projects?
- The approval process is included on Professional. See the approval process page.
- Does Lyyli publish content to channels?
- Lyyli manages communications work from idea to approved content. Ready content is taken to your organisation's existing publishing channels.
Related pages
Want to see what a shared communications workflow could look like for your team?
Book a demo and we will walk through how Lyyli fits your communications team's day-to-day work.