<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alexander Zorychta on Medium]]></title>
        <description><![CDATA[Stories by Alexander Zorychta on Medium]]></description>
        <link>https://medium.com/@azorychta?source=rss-5d0282bf0d6a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_bF2ses_ThEMSfxzHTudQA.jpeg</url>
            <title>Stories by Alexander Zorychta on Medium</title>
            <link>https://medium.com/@azorychta?source=rss-5d0282bf0d6a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 14:22:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@azorychta/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to: Use Claude 3.5 with VertexAI on Firebase Firestore & storing as JSON]]></title>
            <link>https://towardsdev.com/how-to-use-claud-3-5-with-vertexai-on-firebase-firestore-storing-as-json-2aa5edd6aaa8?source=rss-5d0282bf0d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2aa5edd6aaa8</guid>
            <category><![CDATA[firebase-cloud-functions]]></category>
            <category><![CDATA[vertex-ai]]></category>
            <category><![CDATA[claude-3-5-sonnet]]></category>
            <category><![CDATA[http-request]]></category>
            <category><![CDATA[json]]></category>
            <dc:creator><![CDATA[Alexander Zorychta]]></dc:creator>
            <pubDate>Sun, 30 Jun 2024 14:19:11 GMT</pubDate>
            <atom:updated>2024-07-02T23:31:55.941Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q8kXjbq3WtvXyTFy" /><figcaption>Photo by <a href="https://unsplash.com/@joelfilip?utm_source=medium&amp;utm_medium=referral">Joel Filipe</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Finding this is impossible online, and should be easily available.</p><p>If you are using Firebase’s cloud functions and want to process information through an AI Model, you may think you are stuck with Gemini 1.5. Well, first of all, do NOT use Gemini, it’s awful and does not produce the same results as in their Generative AI Studio.</p><p>VertexAI is Google’s platform for using AI models, but it’s not just limited to Gemini — they have a partnership with Anthropic to let you use Claude 3.5 on VertexAI.</p><p>Claude 3.5 is the best model out there and super easy to use as well. The hard part is setting it up if you want to use it with Firebase Functions because the documentation out there isn’t clear. They offer an SDK for Python and TypeScript, but you need to use HTTP Requests for anything else… like JS.</p><p>Here is the exact JS code you can use in your Cloud Functions if you want to use Claude 3.5 through Vertex, and I included comments for you so you can customize and build something more complex.</p><p>An added bonus is you can see here how to handle a JSON response returned by Claude 3.5 as well (useful for storing into Firestore).</p><p>Give me some claps if you found this useful!</p><pre>const functions = require(&#39;firebase-functions&#39;);<br>const admin = require(&#39;firebase-admin&#39;);<br>const { GoogleAuth } = require(&#39;google-auth-library&#39;);<br>const https = require(&#39;https&#39;);<br><br>exports.yourFunctionName = functions.runWith({ //optional<br>  timeoutSeconds: 540, //if you want the function to run longer because you are sending more to the AI<br>  memory: &#39;4GB&#39; //if you want to increase the allowed memory usage<br>}).firestore<br>  .document(&#39;collection/document/subcollection/{docId}&#39;)<br>  .onCreate(async (snap, context) =&gt; { //this function triggers when new doc is created in Firestore<br>      const PROJECT_ID = &#39;YOUR-GOOGLE_PROJECT_ID&#39;;<br>      const MODEL = &#39;claude-3-5-sonnet@20240620&#39;; //newest model<br>      const LOCATION = &#39;us-east5&#39;; //also one in Europe<br><br>      try {<br>          const data = snap.data();<br>          if (!data || !data.body) {<br>              throw new Error(&#39;Document data or body field is missing&#39;);<br>          } //some error handling<br>          const contentToAnalyze = data.body; //what you want the AI to look at<br>          const docId = context.params.docId;<br><br>          // Initialize Google Auth<br>          const auth = new GoogleAuth({<br>              scopes: [&#39;https://www.googleapis.com/auth/cloud-platform&#39;]<br>          }); // You are accessing Claude through Google, so you need to log in.<br><br>          // Get the access token<br>          const token = await auth.getAccessToken(); // token for google login<br><br>          const options = { // Consider this like filling out the address on a postal envelope<br>              hostname: `${LOCATION}-aiplatform.googleapis.com`,<br>              path: `/v1/projects/${PROJECT_ID}/locations/${LOCATION}/publishers/anthropic/models/${MODEL}:streamRawPredict`,<br>              method: &#39;POST&#39;,<br>              headers: {<br>                  &#39;Authorization&#39;: `Bearer ${token}`,<br>                  &#39;Content-Type&#39;: &#39;application/json; charset=utf-8&#39;<br>              }<br>          };<br><br>          <br>           // Create Document object - what you&#39;re eventually going to store in Firestore<br>           const firestoreModelDocInfo = {<br>            id: docId,<br>            title: data.subject, //example field<br>            createdAt: admin.firestore.FieldValue.serverTimestamp() //example field<br>        };<br><br>        const promptNames = [&#39;protein&#39;,&#39;sky&#39;]; //to look up a series of prompts<br><br><br>          const askPromises = promptNames.map(promptName =&gt; {<br>              const prompt = prompts[promptName];<br>              const postData = JSON.stringify({<br>                  anthropic_version: &quot;vertex-2023-10-16&quot;,<br>                  messages: [<br>                      {<br>                          role: &quot;user&quot;,<br>                          content: [<br>                              {<br>                                  type: &quot;text&quot;,<br>                                  text: prompt + contentToAnalyze, //this puts the two together. You could just make it simple and stick your prompt here<br>                              }<br>                          ]<br>                      }<br>                  ],<br>                  max_tokens: 4096,<br>                  stream: false<br>              });<br><br>              return makeHttpRequest(options, postData); //send to Claude<br>          });<br><br>          const responses = await Promise.all(askPromises);<br><br>          <br>          responses.forEach((response, index) =&gt; {<br>            const prompt = prompts[index];<br>            console.log(`Raw response for ${prompt}:`, response.content[0].text);<br>            <br>            try {<br>                const parsedResponse = extractAndParseJSON(response.content[0].text);<br>                <br>                // Apply cleanup function if it exists - you would need to make these if you need further help processing Claude&#39;s answers.<br>                if (cleanupFunctions[prompt]) {<br>                    firestoreModelDocInfo[prompt] = cleanupFunctions[prompt](parsedResponse);<br>                } else {<br>                    firestoreModelDocInfo[prompt] = parsedResponse;<br>                }<br>            } catch (error) {<br>                console.error(`Error processing response for ${prompt}:`, error);<br>                firestoreModelDocInfo[prompt] = [];  // Set to empty array if parsing fails<br>            }<br>        });<br><br><br><br>          // Save the firestoreModelDocInfo to Firestore<br>          await admin.firestore().collection(&#39;firestoreModelDocInfos&#39;).doc(docId).set(firestoreModelDocInfo);<br><br>        } catch (error) {<br>            console.error(&#39;Error:&#39;, error);<br>            // Log the error to Firestore or your preferred logging service<br>            await admin.firestore().collection(&#39;errors&#39;).add({<br>                error: error.toString(),<br>                stack: error.stack,<br>                docId: context.params.docId,<br>                timestamp: admin.firestore.FieldValue.serverTimestamp()<br>            });<br>        }<br>        <br>  });<br><br>    const prompts = { protein: `Which foods have the highest protein?`, <br>                      sky: `Why is the sky blue?`  <br>};<br>    <br><br>// Function that sends the HTTP Request. Do not mess with<br><br>function makeHttpRequest(options, postData) {<br>    return new Promise((resolve, reject) =&gt; {<br>      const req = https.request(options, (res) =&gt; {<br>        let data = &#39;&#39;;<br>        res.on(&#39;data&#39;, (chunk) =&gt; {<br>          data += chunk;<br>        });<br>        res.on(&#39;end&#39;, () =&gt; {<br>          resolve(JSON.parse(data));<br>        });<br>      });<br>  <br>      req.on(&#39;error&#39;, (error) =&gt; {<br>        reject(error);<br>      });<br>  <br>      req.write(postData);<br>      req.end();<br>    });<br>  }<br><br>  function extractAndParseJSON(text) { //makes sure you get it back in the right way<br>    // Find the first occurrence of &#39;[&#39; or &#39;{&#39;<br>    const jsonStart = text.indexOf(&#39;[&#39;) !== -1 ? text.indexOf(&#39;[&#39;) : text.indexOf(&#39;{&#39;);<br>    if (jsonStart === -1) {<br>        throw new Error(&#39;No JSON object found in the response&#39;);<br>    }<br>    <br>    // Find the last occurrence of &#39;]&#39; or &#39;}&#39;<br>    const jsonEnd = text.lastIndexOf(&#39;]&#39;) !== -1 ? text.lastIndexOf(&#39;]&#39;) + 1 : text.lastIndexOf(&#39;}&#39;) + 1;<br>    if (jsonEnd === -1) {<br>        throw new Error(&#39;Invalid JSON structure in the response&#39;);<br>    }<br>    <br>    // Extract the JSON part<br>    const jsonString = text.slice(jsonStart, jsonEnd);<br>    <br>    try {<br>        return JSON.parse(jsonString);<br>    } catch (error) {<br>        throw new Error(`Failed to parse JSON: ${error.message}`);<br>    }<br>}</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2aa5edd6aaa8" width="1" height="1" alt=""><hr><p><a href="https://towardsdev.com/how-to-use-claud-3-5-with-vertexai-on-firebase-firestore-storing-as-json-2aa5edd6aaa8">How to: Use Claude 3.5 with VertexAI on Firebase Firestore &amp; storing as JSON</a> was originally published in <a href="https://towardsdev.com/">Towards Dev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Use Zapier to Update Firebase Firestore Records]]></title>
            <link>https://azorychta.medium.com/how-to-use-zapier-to-update-firebase-firestore-records-19add0e6f656?source=rss-5d0282bf0d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/19add0e6f656</guid>
            <category><![CDATA[firebase]]></category>
            <category><![CDATA[zapier]]></category>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[low-code]]></category>
            <dc:creator><![CDATA[Alexander Zorychta]]></dc:creator>
            <pubDate>Sun, 18 Sep 2022 21:45:45 GMT</pubDate>
            <atom:updated>2022-09-18T21:49:35.927Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re like me, you may have been disappointed to see that while you can create Firestore records with Zapier, you can’t edit them. Ah, the joy of no/low code tools.</p><p>Instead of you spending 2 or 3 hours trying to figure it out, here’s one way to solve it.</p><h3>What You’ll Need</h3><ul><li>Firebase Firestore database</li><li>Zapier</li><li>Firebase Functions set up in a</li><li>Code Editor like Visual Studio</li></ul><h3>How It Works</h3><h4>1. Write this Cloud Function and deploy it into your Functions on Firebase.</h4><pre>exports.functionName = functions.https.onRequest(async (req, res) =&gt; {</pre><pre>await admin //Firestore function to update a document<br>.firestore()<br>.collection(“users”)<br>.doc(req.query.docId)<br>.update({<br>fieldToBeUpdated: req.query.fieldName<br>});</pre><pre>res.status(200).send(‘success’);</pre><pre>});</pre><p>When you deploy it, grab the URL of the function. Should be something like <a href="https://xxxxxxx.cloudfunctions.net/functionName">https://xxxxxxx.cloudfunctions.net/functionName</a></p><h4>2. In Zapier, set up a Webhook.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWDPGhYeT7d6U8EAa80DlA.png" /></figure><p>Set it as GET.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QNAKH5cnBrw9cT2Y3_zwZw.png" /></figure><p>Enter the function URL. As query string params, add in any values you need to update the record, such as the documentId you are trying to change as well as the fieldName you want to change in the document.</p><p>DO NOT send as JSON.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6WIAxix6mMDRuYPdA4rY8Q.png" /></figure><p>Test and make sure it sends the response back.</p><p>You’re done!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19add0e6f656" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Composing Email on iOS via Custom URL Schemes]]></title>
            <link>https://azorychta.medium.com/composing-email-on-ios-via-custom-url-schemes-7d408ae5b0aa?source=rss-5d0282bf0d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d408ae5b0aa</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[url]]></category>
            <category><![CDATA[email]]></category>
            <dc:creator><![CDATA[Alexander Zorychta]]></dc:creator>
            <pubDate>Mon, 11 Jan 2021 04:26:54 GMT</pubDate>
            <atom:updated>2021-01-11T04:26:54.692Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re developing an app for iOS, you might want to open an email application with the click of a button from your own app. You also might want to go directly to a compose email screen with pre-filled information. Here’s how you do it for each mail application.</p><p>Because I had to search far and wide for this information, I would like this to be easily found for anyone else!</p><ul><li>Default Mail App</li><li>Mail</li><li>Gmail</li><li>Outlook</li><li>Spark</li><li>Airmail</li><li>Yahoo Mail</li><li>Fastmail</li><li>Dispatch</li></ul><p><em>One thing to note — the variables recipient, subject, and message all must be encoded to be used as a URL. For example, all spaces are turned into %20.</em></p><h3>Default Mail App</h3><p>As of iOS 14.0, you can set the default mail app to not just be Mail.</p><p><strong>Open the app: </strong><br>You can open with</p><blockquote>mailto:</blockquote><p><strong>Compose:</strong></p><blockquote>mailto:?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><h3>Mail</h3><p><strong>Open the app: </strong><br>You can open this with</p><blockquote>message://</blockquote><p><strong>Compose:</strong><br>As far as I know, you can’t pre-fill the Mail app directly unless it is default. See the Default Mail App section for a workaround that only works if it is the default mail app.</p><h3>Gmail</h3><p>The most popular, by far.</p><p><strong>Open the app: </strong><br>You can open with</p><blockquote>googlegmail://</blockquote><p><strong>Compose:</strong></p><blockquote>googlegmail:///co?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><p>Note the THREE forward slashes in the beginning, and that Gmail decided to shorten ‘compose’ into ‘co.’</p><h3>Outlook</h3><p><strong>Open the app: </strong><br>You can open with</p><blockquote>ms-outlook://</blockquote><p><strong>Compose:</strong></p><blockquote>ms-outlook://compose?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><h3>Spark</h3><p><strong>Open the app: </strong><br>You can open with</p><blockquote>readdle-spark://</blockquote><p><strong>Compose:</strong></p><blockquote>readdle-spark://compose?recipient=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><p>Spark decided to rename ‘to’ to be ‘recipient’.</p><h3>Airmail</h3><p><strong>Open the app: </strong><br>You can open with</p><blockquote>airmail://</blockquote><p><strong>Compose:</strong></p><blockquote>airmail://compose?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;plainBody=<strong>[message]</strong>&amp;htmlBody=<strong>[message]</strong></blockquote><p>Spark decided to rename ‘to’ to be ‘recipient’. They also get fancy in that they specify two different body types.</p><p><strong>Extra Parameters:</strong></p><blockquote>from=<strong>[from]</strong></blockquote><blockquote>cc=<strong>[cc]</strong></blockquote><blockquote>bcc=<strong>[bcc]</strong></blockquote><h3>Yahoo Mail</h3><p>Does anyone actually still use this?</p><p><strong>Open the app: </strong><br>You can open with</p><blockquote>ymail://</blockquote><p><strong>Compose:</strong></p><blockquote>ymail://mail/compose?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><p>Yahoo inserts an extra mail folder in between!</p><h3>Fastmail</h3><p>Another oldie but goodie.</p><p><strong>Open the app: </strong><br>You can open with</p><blockquote>fastmail://</blockquote><p><strong>Compose:</strong></p><blockquote>fastmail://mail/compose?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><p>Fastmail also inserts an extra mail folder in between!</p><h3>Dispatch</h3><p>Never heard of this, but here’s the details!</p><p><strong>Open the app: </strong><br>You can open with</p><blockquote>x-dispatch://</blockquote><p><strong>Compose:</strong></p><blockquote>x-dispatch:///compose?to=<strong>[recipient]</strong>&amp;subject=<strong>[subject]</strong>&amp;body=<strong>[message]</strong></blockquote><p>Dispatch is the only other one to have three slashes.</p><h3>That’s all!</h3><p>Let me know if I missed anything!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dyBCxRjGXpO8Uxly" /><figcaption>Photo by <a href="https://unsplash.com/@hostreviews?utm_source=medium&amp;utm_medium=referral">Stephen Phillips - Hostreviews.co.uk</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d408ae5b0aa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why and How to Craft a Stakeholder Update]]></title>
            <link>https://azorychta.medium.com/why-and-how-to-craft-a-stakeholder-update-7bd169761743?source=rss-5d0282bf0d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bd169761743</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[venture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Alexander Zorychta]]></dc:creator>
            <pubDate>Fri, 10 Jul 2020 21:05:37 GMT</pubDate>
            <atom:updated>2020-07-10T21:20:32.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TexyOPx9Px_FKbl1UGJx0A.jpeg" /></figure><p>Being a founder of a venture is hard. Finding and conducting interviews, balancing team dynamics, gaining traction, managing MVP build-out, and the myriad of roughly defined tasks of ambiguous priority and payoff can keep you in the weeds. Not only that, all of the above can often leave you working toward the wrong goals. It can prove difficult to come up for air and make time for important but small tasks that can help your venture take a giant leap forward.</p><p>But there is one task that separates the consistently successful founders from the rest of the pack. This one task is one that many of the ventures I have worked with have found great value in. Presenting: the Stakeholder Update.</p><h4>What’s a Stakeholder Update?</h4><p>A stakeholder update is a regular message to all of your supporters telling them what you’re up to and what you need help with.</p><p>This comes from the practice of an Investor Update common among mature companies. Recently, founders have begun to realize that this is extremely helpful even from the beginning.</p><h4><strong>Why craft a Stakeholder Update?</strong></h4><p>The most valuable resource an entrepreneur has is the network of people they know who support them and what they’re building. In effectuation (the logic used by expert entrepreneurs), this is part of the <a href="https://www.effectuation.org/?page_id=4055&amp;principle=bird-in-hand">bird-in-hand</a> principle. Start with who you are, what you know, and <em>who you know</em>. Meaningful action in entrepreneurship is either 1) building something or 2) gaining commitment from someone who can help you.</p><p>Founders have found all kinds of benefits from these Stakeholder Updates. They’ve gotten feedback on prototypes, funding connections, beta testers, partnership opportunities, news coverage, suppliers, new mentors, and even co-founders.</p><p>As mentioned before, most entrepreneurs are so busy focusing on building the product, or understanding the problem they’re solving, or developing the business model that they often do not leverage this most valuable resource they have.</p><p>You potentially hundreds of people that support you who may know something or someone that you don’t. The Stakeholder Update is a great way to keep them in the loop and enlist them to be extra eyes and ears for the success of your venture.</p><h4><strong>How to design a Stakeholder Update</strong></h4><p>Now, as with most things, the devil is in the details, and proper execution will ensure this task doesn’t impede your workflow as an entrepreneur, while also yielding maximum value from everyone around you who supports you in your venture.</p><p>A well-done Stakeholder Update accomplishes the following:</p><ul><li>Keeps you in regular touch with those who support you</li><li>Seeks help with things that are hard for you but easy for those who in your support network</li><li>Does not inconvenience those people who read it</li><li>Does not impede your workflow as an entrepreneur</li></ul><p>With these goals in mind, here are the design criteria I’ve found most impactful</p><p><strong>Make it regular.</strong> If you do it once, it’s useless. The magic comes from staying in regular touch with these people who support you. Too many entrepreneurs go radio silent to their supporters, and come around later asking for a big favor (like raising money or asking people to buy their product). Out of sight is out of mind. <em>You want to send this no more frequently than biweekly, but no less frequently than monthly.</em></p><p><strong>Include everyone who supports you. </strong>Think big. Don’t just include your friends, mentors, or advisors. Every interview you have with a potential stakeholder or potential customer, ask them if they want to be included. Add them.</p><p><strong>Make it plain. </strong>Just text, no HTML. Don’t worry about a great template with branding and lots of frills like articles related to your industry. If you’re spending your time making a beautiful stakeholder update, it signals to your stakeholders that you aren’t spending that time working on your business.</p><p><strong>Make it simple. </strong>As one founder put it, “If you have to edit your update more than 3 times, you’re overthinking it.”</p><p><strong>Make it short. </strong>If it’s too long, people won’t read it. They’ll open it, realize it’s long, and save it for later. You want them to open it, read it, smile at your progress, empathize with your obstacles, and make a quick suggestion or connection in response to your asks for help.</p><p><strong>Show results, no matter how small. </strong>The first of three sections you should include is a “Highlights” section. No more than three bullet points that are no more than one line each. Tell them about your wins, no matter how small. In the beginning, they can be intangible and personal. However, as soon as you can, aim for objective measures. These could be incredibly simple and honest metrics like daily active users, revenue, posts, letters of intents, conversion rate, cost of acquisition, leads, etc. Nothing excites supporters more than seeing objective measures showing actual (compared to vanity metric) progress.</p><p><strong>Show vulnerability. </strong>This is the section most founders omit. Don’t. It’s important. You should be including a “Lowlights” section. Why? It puts your highlights into perspective. A venture is not a straight line. If you don’t have lowlights, you aren’t digging into your assumptions, and so it signals that you aren’t actually working on the right things as a venture. Aim for three bullet points of no more than one line each. <em>Additionally, your tone should lean more casual and informal rather than professional and cold. These are people who support you, and believe in you as a founder. Don’t be afraid to show your personality!</em></p><p><strong>Ask for help. </strong>The final section is the “Asks” section. Again, three bullet points of no more than one line each. It doesn’t matter what you ask for, <em>as long as it’s specific</em>. You could ask for help connecting to a particular influential person, or someone with a particular background or skill set, or help with a specific part of the technical aspect of your MVP. The best intro requests are for specific individuals; second best are for specific roles.</p><h4>Which medium should I use?</h4><p><strong>In the beginning, when your list is short: </strong>Consider BCC’ing your supporters from your current email account. This works in the short-term because you don’t need to go set up an email campaign platform, and your BCC list email won’t go to spam because everyone on the list has already received emails from you. <em>Note: if you set up a new account mycompany@gmail.com and try to BCC everyone with your first email, it’s definitely going to go to spam.</em></p><p><strong>As it grows: </strong>Consider setting up an email campaign platform, such as MailChimp. Warning: don’t be tempted to set up a beautiful email template. Follow the guidelines above, especially around <strong><em>plain and simple</em></strong><em>.</em></p><h4><strong>An Example Template:</strong></h4><p>Hello everyone!</p><p>If you are receiving this email, you are someone who has graciously shared your time and experience with us. Thank you! We really appreciate how much you have helped us grow over the past few months. If you are new to these updates, welcome!</p><p><strong>Highlights</strong></p><ul><li>Won $10k in grants and competition prize money,</li><li>Completed 25 more customer discovery interviews with those in the aerospace industry.</li><li>17% month-over-month revenue growth in the last 6 months.</li></ul><p><strong>Lowlights</strong></p><ul><li>Demoed to one clinic (buyer) and they were more interested in the software feature than the hardware we spent most of the last 10 months building.</li><li>We did not advance in the Rice Business Plan Competition.</li><li>COVID-19 will slow everything down for a while. We applied for an SBA Disaster Loan to attempt and keep development going instead of pausing everything completely.</li></ul><p><strong>Asks.</strong></p><ul><li>Do you know anyone who has experience selling to physical therapy clinics?</li><li>Do you know anyone in the Veterans Affairs that we can speak with?</li><li>Do you know any active members in the military/DOD who we can talk to?</li></ul><p><strong>(Bonus Attached: One or two pictures of something you built.)</strong></p><h4><strong>My Ask to You</strong></h4><p>Hopefully I’ve convinced you to start doing these, if you aren’t already. The hard part is making sure you send them on a regular basis for maximum effect. While there is of course no singular recipe for success as a founder, my experience has shown me that certain habits are indeed shared across many entrepreneurs who’ve managed to break through. On their short list? Stakeholder Updates.</p><h4><strong>Further Reading</strong></h4><ol><li>Daniel Gross’<a href="https://dcgross.com/investor-updates/"> How to Write Investor Updates</a> (for communicating with investors)</li><li><a href="https://medium.com/linear-app/startups-write-changelogs-c6a1d2ff4820">Startups, Write Changelogs</a> (really useful for the product side of things)</li></ol><p><em>Thanks to Damon DeVito, startup mentor whose insistence on these stakeholder updates has led to the success of many startups in our community.</em></p><p><em>Thanks to Victor Layne, Patt Eagan, David Huang, Drew Lytle, Aditya Narayan, Danya Abutaleb, Jack Herrmann, Anisha Sharma, Rodney Davis, Joe Jamison, Vinny Sciortino, Chris Dauber, Alec Brewer, Alvaro Anspach, George Ardura, Taylor Kamhong, Joe Kilroy, Sahil Parikh, Carolyn Zelikow, and Kevin Seitter for their feedback on this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bd169761743" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Strangers to Best Friends in 45 Minutes]]></title>
            <link>https://azorychta.medium.com/from-strangers-to-best-friends-in-45-minutes-e1be0f472306?source=rss-5d0282bf0d6a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1be0f472306</guid>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Alexander Zorychta]]></dc:creator>
            <pubDate>Sat, 30 Jun 2018 00:00:00 GMT</pubDate>
            <atom:updated>2018-08-17T03:13:26.847Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2wPqdTOlDBMnaNfH" /><figcaption>In the midst of deep discussions.</figcaption></figure><p>Last week, I had the pleasure of attending the Creative Problem Solving Institute (<a href="http://cpsiconference.com/">CPSI</a>), where I was able to experience the applications and nuances of this method for harnessing deliberate creativity, the <a href="http://www.creativeeducationfoundation.org/creative-problem-solving/the-cps-process/">Creative Problem Solving process</a>. One amazing part of the conference is that anyone can propose 60 minute session called night flights to try out experimental workshops.</p><p>I decided to try out one I had only done once before, whose purpose is to forge strong relationships between strangers in just 45 minutes. Sounds incredible, right?</p><p>Did it work?</p><h3>Yes, it actually worked.</h3><p>At the beginning of the workshop, I asked people to find a person they didn’t know and who they thought they they might have the least in common with. All of them were at a 1 out of 7.</p><p>By the end of the workshop, we may not have created super best friends, but the difference in relationship closeness is astounding. On average, the participants reported moving from a 1 to a 5.3 out of 7 in relationship closeness.</p><p>During the session, there was a good mix of laughter, and about a third of the participants broke down into tears while talking with their partner who had been only a stranger an hour before.</p><p>Overall, participants were believers at the end. After the hour, I then tried to get them to go to the bar together as a group, but most of the room just stayed in their same spot and continued conversation with their partner for another hour.</p><p>What was interesting was that the pairs kept referring to their partner as Best Friend throughout CPSI and became really excited whenever they saw one another. What’s more is that the workshop was talked about all throughout the rest of the conference. I wish I could have captured this feedback.</p><p>As a first timer at this conference, I didn’t expect so much positive feedback that even the keynote speakers of the conference would seek me out to learn more about what I did in this workshop.</p><h3>Implications on the Success of This Session</h3><p>Okay, so we can bring strangers closer in 45 minutes. What does this mean in the larger context of the world?</p><p>In <a href="https://engineering.virginia.edu/faculty/alexander-zorychta">my role</a> at the University of Virginia, my primary role is to enhance the individual and team connections between student entrepreneurs so they will be more successful long-term. This is because it has been shown that trust and familiarity are the foundational elements of a successful startup, even more importantly than functional diversity, skills, or knowledge ( <a href="https://www.jstor.org/stable/pdf/1519766.pdf?casa_token=gg-sWR2URcMAAAAA:jKHfPkLZAuEXSYNiJ1Mf9aKBOCdw7F7JHOIQaYwcWAfxQFXTqUVjSLAnnn1QhpSgEUIMqtQUCPFD8g0M_RlFwLyHZbLuERxByzuRuxMgGNovNXnc9Q">Ruef et al., 2003</a>). These latter three things are important, but not as important as trust and familiarity in the success of a team.</p><p><strong>Wouldn’t it be great if we could reduce the barriers to trust and familiarity among those who are functionally diverse to create rockstar teams that will be able to pull from a variety of experiences to solve the greatest challenges facing humanity?</strong></p><p>Trust and familiarity come from those who associate closely with each other, in groups that provide “closure” for enforcing social norms. Unfortunately, due to homophily (the tendency of people to associate with those that they perceive to be like themselves), those that we develop trust and familiarity with are typically similar to us in some way. Classmates, sports teammates, childhood friends, etc.</p><p>As a result, many co-founder teams may lack the essential element of functional diversity from the outset.</p><h3>Where This Idea Came From</h3><p>Last semester, I had <a href="http://c4i.splashthat.com/">experimented with teaching</a> early student Engineering entrepreneurs the creative problem solving process as a way to discovery high quality opportunities that they would be excited to move forward with past the class.</p><p>Our previous research has indicated that the most important part of an entrepreneurial journey is the people that the entrepreneur surrounds themselves with (<a href="https://www.asee.org/public/conferences/78/papers/19983/view">Zorychta &amp; Pyle, 2017</a>).</p><p>Using this as a framework, I knew that what was more valuable than any tool I could give them would be providing the space for cultivating meaningful relationships built on trust and familiarity between these highly engaged students. I searched for activities that might provide for this; I found tools to help with self-awareness, and tools for teambuilding, but I was lacking in an established activity to create powerful relationships between individuals.</p><p>I decided to develop a session based on an <a href="https://www.nytimes.com/2015/01/11/fashion/no-37-big-wedding-or-small.html">article in the New York Times</a> that went viral in 2015. It was based upon a psychological study that laid out a method and showed results for forging strong relationships between those who were initially strangers. We had such success with it in my Creativity for Invention class, that I decided to use it for CPSI.</p><h3>The Basic Outline of the Workshop</h3><p>The format was pretty basic. It took so little facilitation that I actually ended up participating it in myself. As far as <em>what </em>I did, I dug past the NY Times article that made this concept viral, and looked into the <a href="http://journals.sagepub.com/doi/pdf/10.1177/0146167297234003">actual published paper of the psych study</a> and copied their Methods section as my facilitation guide.</p><p>Essentially, it is three sets of questions that get more in-depth. For each set, you allot fifteen minutes. Partners take turns asking each other the same questions, moving down the list. The person asking the particular question first alternates with each question, so there is an equality and not a prime interviewer. Then, there is a final step in which pairs of participants share prolonged, unbreaking eye contact for five minutes.</p><h3>Impromptu Changes to the Facilitation Plan</h3><p>From this basic outline, I did a lot of experimentation in my facilitation according to what the energy of the room was and when I saw opportunities to make a more impactful experience. I will give three examples.</p><p>For instance, to choose partners, I did not randomly assign them. I had planned to ask them to find a stranger in the room with whom they believed they had the least in common. Then, in the moment, I thought that it might be most impactful for them to lock eyes with one another so I could figure out who was still unpaired. This initial eye contact proved to be very significant for the rest of the session, and yet was unplanned initially.</p><p>Second, I had initially intended for the partners to at least share some initial information about one another, such as name, hometown, and some small talk. I decided to nix this as soon as the volume of the room became loud after the partners found one another. I told them to only share nonverbal communication at first — this was mainly so I could make sure everyone had a partner and was ready to begin. This is an example of what I learned to be the “fourth rule of Improv,” called Cut With Energy (shoutout to <a href="https://bigbluedoor.org/">Big Blue Door</a> for teaching me that!)</p><p>The unintended consequence of this is that it built the anticipation, and made the “locked eyes” part of the experience that much more impactful, and it set a blank slate for their relationship and allowed them to dive deeply into a relationship with someone without even knowing their name.</p><p>Finally, I made it fun by getting everyone on board to try to “replicate” this scientific study. I explained how it was found that <a href="http://www.apa.org/monitor/2015/10/share-reproducibility.aspx">possibly half of psychology studies’ findings are not reproducible</a>, and that we had to follow these methods to the T to make sure we would actually become best friends. The gave a sense of adventure and shared purpose for the group.</p><h3>In what ways might we provide more meaningful experiences like this?</h3><p>I’m hoping to find and develop more mechanisms like this session, “Did We Just Become Best Friends?”</p><p>If you’re interested in talking more about this, I’d love to discuss. I’m also looking for more opportunities to facilitate workshops like this that create stronger connections between people. Let me know if you’re looking for someone with high energy and enthusiasm to facilitate them.</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/from-strangers-best-friends-45-minutes-alexander-zorychta/"><em>https://www.linkedin.com</em></a><em> on June 30, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1be0f472306" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>