Craft and publish engaging content in an app built for creators.
NEW
Publish anywhere
Post on LinkedIn & Mastodon too. More platforms coming soon.
Make it punchier š
Typefully
@typefully
We're launching a Command Bar today with great commands and features.
AI ideas and rewrites
Get suggestions, tweet ideas, and rewrites powered by AI.
Turn your tweets & threads into a social blog
Give your content new life with our beautiful, sharable pages. Make it go viral on other platforms too.
+14
Followers
Powerful analytics to grow faster
Easily track your engagement analytics to improve your content and grow faster.
Build in public
Share a recent learning with your followers.
Create engagement
Pose a thought-provoking question.
Never run out of ideas
Get prompts and ideas whenever you write - with examples of popular tweets.
@aaditsh
I think this thread hook could be improved.
@frankdilo
On it š„
Share drafts & leave comments
Write with your teammates and get feedback with comments.
NEW
Easlo
@heyeaslo
Reply with "Notion" to get early access to my new template.
Jaga
@kandros5591
Notion š
DM Sent
Create giveaways with Auto-DMs
Send DMs automatically based on engagement with your tweets.
And much more:
Auto-Split Text in Posts
Thread Finisher
Tweet Numbering
Pin Drafts
Connect Multiple Accounts
Automatic Backups
Dark Mode
Keyboard Shortcuts
Creators loveĀ Typefully
150,000+ creators andĀ teams chose Typefully to curate their Twitter presence.
Marc Kƶhlbrugge@marckohlbrugge
Tweeting more with @typefully these days.
š Distraction-free
āļø Write-only Twitter
š§µ Effortless threads
š Actionable metrics
I recommend giving it a shot.
Jurre Houtkamp@jurrehoutkamp
Typefully is fantastic and way too cheap for what you get.
Weāve tried many alternatives at @framer but nothing beats it. If youāre still tweeting from Twitter youāre wasting time.
DHH@dhh
This is my new go-to writing environment for Twitter threads.
They've built something wonderfully simple and distraction free with Typefully š
Santiago@svpino
For 24 months, I tried almost a dozen Twitter scheduling tools.
Then I found @typefully, and I've been using it for seven months straight.
When it comes down to the experience of scheduling and long-form content writing, Typefully is in a league of its own.
After trying literally all the major Twitter scheduling tools, I settled with @typefully.
Killer feature to me is the native image editor ā unique and super useful š
Visual Theory@visualtheory_
Really impressed by the way @typefully has simplified my Twitter writing + scheduling/publishing experience.
Beautiful user experience.
0 friction.
Simplicity is the ultimate sophistication.
Queue your content inĀ seconds
Write, schedule and boost your tweets - withĀ noĀ need forĀ extra apps.
Schedule with one click
Queue your post with a single click - or pick a time manually.
Pick the perfect time
Time each post to perfection with Typefully's performance analytics.
Boost your content
Retweet and plug your posts for automated engagement.
Start creating a content queue.
Write once, publish everywhere
We natively support multiple platforms, so that you can expand your reach easily.
Check the analytics thatĀ matter
Build your audience with insights that makeĀ sense.
Writing prompts & personalized postĀ ideas
Break through writer's block with great ideas and suggestions.
Never run out of ideas
Enjoy daily prompts and ideas to inspire your writing.
Use AI for personalized suggestions
Get inspiration from ideas based on your own past tweets.
Flick through topics
Or skim through curated collections of trending tweets for each topic.
Write, edit, and track tweetsĀ together
Write and publish with your teammates andĀ friends.
Share your drafts
Brainstorm and bounce ideas with your teammates.
NEW
@aaditsh
I think this thread hook could be improved.
@frankdilo
On it š„
Add comments
Get feedback from coworkers before you hit publish.
Read, Write, Publish
Read, WriteRead
Control user access
Decide who can view, edit, or publish your drafts.
CYCLE TIME VANITY!
Most people will take it for granted that if we perform work in less time, it must be better. Right?
All the mainstream approaches - #SAFe, #Scrum, #Kanban, #DevOps - obsessively insist that reducing Cycle Time is a Good Thing(tm)!
Or is it?
We primed ourselves to be open to what is not self-evident from the outset, but obvious hind sight.
We used the Story of the Egg of Columbus to get this idea across.
Deeper knowledge will afford us non-conventional thinking.
twitter.com/tendon/status/1523949167587905536
It's like the proverbial two sided coin.
It is not only about finding counter-intuitive solutions to our problems.
It is also to be ready to question what appear to be obvious solutions to well known problems.
Cycle Time reduction is of this nature.
Who in their right mind would ever question that reducing Cycle Time would not be a good thing?
(Besides, "Cycle Time" is the time from start to finish of an activity. In TameFlow I prefer to use the term "Flow Time" - but stick to "Cycle Time" here because of familiarity.)
Let's consider this thought experiment (another MENTAL MODEL).
An activity typically takes 10 days to perform.
There are two improvement proposals.
One will reduce the time to 9 days.
The other will increase it to 11 days.
Which do you pick?
No brainer! Right?
The 9 days solution!
Only a madman would go from 10 to 11 days.
This other proposal is even _increasing_ Cycle Time.
Of course it must be discarded!
But let's have some additional information.
The original activity of 10 days is broken down into three sub-activities taking respectively 3, 5, and 2 days (total 10).
First proposal changes to: 2, 5, and 2 (total 9).
Second proposal changes that to: 3, 4 and 4 (total 11).
The slowest activity was 5 days. It is the WORK PROCESS CONSTRAINT. It limits what the entire process can deliver.
The first proposal leaves the second step unchanged.
The second proposal reduces the second step from 5 to 4 days.
So the original process will have an effective OPERATIONAL THROUGHPUT of 1 item every 5 days; or 0.2 items per day.
The first proposal - despite the overall reduction in cycle time from 10 to 9, will still deliver 0.2 items per day.
So it really brings no improvement at all!
The second proposal reduces the second step from 5 to 4 days.
So the second proposal, despite the **overall increase in cycle time** from 10 to 11, will deliver 1 item every 4 days; or 0.25 items per day.
Conclusion:
First proposal with 10% cycle time reduction has zero impact on performance!
Second proposal with a 10% increase on cycle time will produce a 25% increase in performance: from 0.2 to 0.25 items per day.
Unbelievable!
Moral of this story.
Don't mindlessly pursue cycle time reduction.
Most of the time, the effort is vain.
And if you celebrate the gain, you are celebrating a vanity metric!
The only way to improve is to reduce the FLOW TIME of the WORK PROCESS CONSTRAINT.
This also explains, yet again, how operational performance improvements that might be celebrated as victories, at the end of the day delivery zero impact; yet the company sustains the cost of change, for a total loss!
The only improvement that matters is on the Constraint!
Did you enjoy this mind-boggling example?
It is taken out of Chapter 5, "Where to Focus Improvement Efforts" from "The Book of TameFlow".
leanpub.com/tameflow