Writing in Future Past

Shreyas Prakash headshot

Shreyas Prakash

We lack frequent usage of the future past tense in modern discourse.

When I was recently drafting my new year resolutions, I noticed the use of ‘I can’, and ‘I will’, and found myself questioning the format, especially when I see that I’m good at making promises, but end up being miserable at keeping them.

I also observed that when I write “I achieved…” instead of “I will achieve..”, I can bypass the doubt and uncertainty that often comes with future planning.

In fact, Sapir-Whorf hypothesis talks about language having an incredible affect on the way we perceive reality. If that’s the case, can we force our minds to envision success as an accomplished fact, rather than a mere possibility? Whatever we think we “will achieve”, what if we have “already achieved it”, and are imagining the journey in retrospect?

This is future past tense.

The best example that could illustrate this future past tense effect is the ‘A Letter’.

Benjamin Zander, conductor of Boston Philharmonic Orchestra gave an innovative “Grade A” assignment to his students. Before the term started, students would describe what they did to earn the A grade, and who they became by the end of the year.

Tired of students holding themselves back in a musical interpretation class for fear of judgement and how they would eventually be graded, Ben invented the practice of Giving them an A:

“Each student in this class will get an A for the course…However there is one requirement you must fulfil to earn this grade: Sometime during the next two weeks, you must write me a letter dated next May, which begins with the words “Dear Mr. Zander, I got my A because…” and in this letter you are to tell, in as much detail as you can, the story of what will have happened to you by next May that is in line with this extraordinary grade”

Conducting Artistry https://www.conductingartistry.com/post/giving-an-a-how-to-immediately-embody-who-you-want-to-be

The format was in the form of a letter dated in the future describing their accomplishments in the past tense. Here is an example from one of the students who had originally attended Zander’s classes and had written it this way:

11 May 2021

Dear Ben,

I got an A because I went on a challenging and rewarding journey of learning how to be fully myself. Before, I was afraid to share my artistry, opinions and self with the world. I hid from uncomfortable things, and ran away from making others uncomfortable too.

I realised this fear was holding me back, so I decided to ditch it!

Now, I am fully myself in the world and in my music-making. I’m not afraid to show people who I am and what I believe. I am unapologetic about what I have to share. I know that I have a unique and valuable contribution to make.

I am able to fully express myself and all my emotions, rather than running from them or stuffing them away. Now I speak honestly, unflinchingly, and listen openly to others.

I am certain and confident of my value to myself and to others. I stopped judging myself, and let go of my fear of discomfort and mistakes. In fact, I now embrace mistakes as a vital part of growing and learning.

Each day I wake up enthusiastic about learn something new. In the past I was daunted, but now I am excited! I jump into scores with curiosity and wonder at what I will discover. I know that each minute I spend brings me closer to understanding the musical gift a composer has entrusted to me.

‍…

Conducting Artistry https://www.conductingartistry.com/post/giving-an-a-how-to-immediately-embody-who-you-want-to-be

I’ve been attempting to use Zander’s A Letter format to write down notes on what I have done for my year ahead (very counter-intuitive). Will be sharing some updates on this if I notice any signs of improvement. After writing this up, I’m highlighting the “prophecies” which have already been realised, and it seems like a fun exercise.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct-management
  2. How I started building softwares with AI agents being non technicalagentic-engineering
  3. Legible and illegible tasks in organisationsproduct
  4. L2 Fat marker sketchesdesign
  5. Writing as moats for humanswriting
  6. Beauty of second degree probesdecision-making
  7. Read raw transcriptsknowledge
  8. Boundary objects as the new prototypesprototyping
  9. One way door decisionsproduct
  10. Finished softwares should existproduct
  11. Essay Quality Rankerobsidian
  12. Export LLM conversations as snippetsbrowser-extension
  13. Flipping questions on its headinterviewing
  14. Vibe writing maximswriting
  15. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  16. How I build greenfield apps with AI-assisted codingai-coding
  17. We have been scammed by the Gaussian distribution clubmathematics
  18. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  19. I was wrong about optimal stoppingmathematics
  20. Thinking like a ship
  21. Hyperpersonalised N=1 learningeducation
  22. New mediums for humans to complement superintelligenceai-coding
  23. Maxims for AI assisted codingai-coding
  24. Personal Website Starter Kitai-coding
  25. Virtual bookshelvesaesthetics
  26. It's computational and AI everythingai-coding
  27. Public gardens, secret routesdigital-garden
  28. Git way of learning to codeai-coding
  29. Kaomoji generatorsoftware
  30. Copy, Paste and Citecuriosities
  31. Style Transfer in AI writingai-coding
  32. Understanding codebases without using codeai-coding
  33. Vibe coding with Cursorai-coding
  34. Virtuoso Guide for Personal Memory Systemsmemory
  35. Writing in Future Pastwriting
  36. Publish Originally, Syndicate Elsewhereblogging
  37. Poetic License of Designdesign
  38. Idea in the shower, testing before breakfastsoftware
  39. Technology and regulation have a dance of ice and firetechnology
  40. How I ship "stuff"software
  41. Weekly TODO List on CLIcli
  42. Writing is thinkingwriting
  43. Song of Shapes, Words and Pathscreativity
  44. How do we absorb ideas better?knowledge
  45. Read writers who operatewriting
  46. Brew your ideas lazilyideas
  47. Vibescreativity
  48. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  49. Compound Interest of Private Notesknowledge
  50. Conceptual Compression for LLMsai-coding
  51. Meta-analysis for contradictory research findingsdigital-health
  52. Beauty of Zettelswriting
  53. Proof of workproduct
  54. Gauging previous work of new joinees to the teamleadership
  55. Task management for product managersproduct
  56. Stitching React and Rails togetherai-coding
  57. Exploring "smart connections" for note takingknowledge
  58. Deploying Home Cooked Apps with Railssoftware
  59. Self Marketing
  60. Repetitive Copypromptingwriting
  61. Questions to ask every decadejournalling
  62. Balancing work, time and focusproductivity
  63. Hyperlinks are like cashew nutswriting
  64. Brand treatments, Design Systems, Vibesdesign
  65. How to spot human writing on the internet?writing
  66. Can a thought be an algorithm?product
  67. Opportunity Harvestingcareers
  68. How does AI affect UI?design
  69. Everything is a prioritisation problemproduct-management
  70. Nowlifestyle
  71. How I do product roastsproduct
  72. The Modern Startup Stacksoftware
  73. In-person vision transmissionproduct
  74. How might we help children invent for social good?social-design
  75. The meeting before the meetingmeetings
  76. Design that's so bad it's actually gooddesign
  77. Breaking the fourth wall of an interviewinterviewing
  78. Obsessing over personal websitessoftware
  79. Convert v0.dev React to Rails ViewComponentsrails
  80. English is the hot new programming languagesoftware
  81. Better way to think about conflictsconflict-management
  82. The role of taste in building productsdesign
  83. World's most ancient public health problemsoftware
  84. Dear enterprises, we're tired of your subscriptionssoftware
  85. Products need not be user centereddesign
  86. Pluginisation of Modern Softwaredesign
  87. Let's make every work 'strategic'consulting
  88. Making Nielsen's heuristics more digestibledesign
  89. Startups are a fertile ground for risk takingentrepreneurship
  90. Insights are not just a salad of factsdesign
  91. Minimum Lovable Productproduct
  92. Methods are lifejackets not straight jacketsmethodology
  93. How to arrive at on-brand colours?design
  94. Minto principle for writing memoswriting
  95. Importance of Whytask-management
  96. Quality Ideas Trump Executionsoftware
  97. How to hire a personal doctor
  98. Why I prefer indie softwareslifestyle
  99. Use code only if no code failscode
  100. Personal Observation Techniquesdesign
  101. Design is a confusing worddesign
  102. A Primer to Service Design Blueprintsdesign
  103. Rapid Journey Prototypingdesign
  104. Directory Structure Visualizercli
  105. AI git commitscli
  106. Do's and Don'ts of User Researchdesign
  107. Design Manifestodesign
  108. Complex project management for productproducts
  109. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  110. Pedagogy of the Uncharted — What for, and Where to?education
  111. Future of Ageing with Mehdi Yacoubiinterviewing
  112. Future of Equity with Ludovick Petersinterviewing
  113. Future of Mental Health with Kavya Raointerviewing
  114. Future of Tacit knowledge with Celeste Volpiinterviewing
  115. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  116. Future of unschooling with Che Vanniinterviewing
  117. Future of work with Laetitia Vitaudinterviewing
  118. How might we prevent acquired infections in hospitals?digital-health
  119. The soul searching yearsentrepreneurship
  120. Design education amidst social tribulationsdesign
  121. How might we assist deafblind runners to navigate?social-design