Turn spoken studio observations into clear, organized critique notes.

A studio critique rewards close observation, yet most students lose their best comments because handwriting stalls the thought. Voice Typing for Art gives you a practical way to keep pace with your eyes: open your critique document, press the shortcut, and speak while you look at the work. Before the session, create one note file per piece and add lines for medium, dimensions, and the assignment prompt. Sit close enough to see surface detail, keep your device at a comfortable angle, and decide on three fixed headings: what you see, what works, and what to change. A stable setup turns a nervous scramble into a repeatable habit, and the first spoken sentence becomes easier every week.
The format of the critique should shape the routine. In a desk crit, one instructor stands beside the work and speaks in short bursts, so keep the note open and add a heading before each burst. In a group critique, comments arrive from several people, so say the speaker's name at the start of every entry and repeat the work's title before the point. For a cold read, where you leave written notes and collect responses later, dictate a short context paragraph first so readers know the assignment. Decide whether you will type during the session or polish afterward. Both approaches work, but switching halfway usually produces fragments. Write the chosen format at the top of the file and follow it without improvising.
Prepare the vocabulary your critique will need before you enter the room. List the names of artists, movements, materials, and processes you expect to mention, then say each one aloud once so the spoken draft stops guessing. If your class uses shorthand such as gouache lay-in or modular grid, add those phrases to the same list. Note the title of each work exactly as it appears on the wall label, including capitalization. Check that the shortcut works in your note app with a two-sentence test before the session begins. When a term still comes out wrong, correct it once in the document and move on; interrupting your observation to fight the tool costs more than a later edit.
Order matters more than volume. Spend the first minute describing the work without evaluation, because that record is hardest to reconstruct later. Then capture the instructor's questions as they were asked, followed by peer reactions, and finally your own response. Leave a blank line between speakers and use a consistent marker such as a dash before each new voice. If the conversation moves faster than you can speak, type a timestamp and a two-term reminder, then return to it during the polish pass. Ask a classmate to note the three most important comments so you can cross-check your own record. End the session by reading your notes back once and marking anything you cannot explain; those gaps are the first thing to resolve.
A credible critique separates description from judgment. Start by speaking what is physically present: the format, the dominant shapes, the palette, the edges, the placement of the focal point, and the way light moves across the surface. Use plain nouns and verbs rather than praise or blame. If you are reviewing a poster, say where the eye lands first and what it passes on the way to the headline. If you are reviewing a ceramic piece, describe the lip, the foot, and the glaze breaks before you discuss intention. This first pass gives you evidence, and evidence keeps the later verdict from floating free of the object in front of you.
Formal language improves quickly when you rehearse it aloud. Build a short list of terms that fit your discipline, such as contrast, hierarchy, rhythm, mass, tension, and negative space, then practice using each one in a sentence about a real piece. Do not stack terms to sound authoritative; one precise observation is stronger than five vague ones. When you dictate, the app adapts punctuation and formatting to the shape of your sentence, so a spoken list becomes an ordered list without extra work. Keep the tone neutral in this section and save enthusiasm or concern for the evaluation. A reader should be able to picture the work from your description alone, even if they never see the image.
Spoken drafting catches the mind in motion, including the half-starts that make a critique honest. Say what you notice, hear it come back as text, and let the next sentence respond to it. When you change your mind mid-sentence, state the correction plainly and continue; the app removes false starts and self-corrections so the final note reads as one clear decision. This is especially useful when a piece is ambiguous and your first reaction is wrong. Record the wrong turn and the reason you abandoned it, because that reasoning often becomes the most useful comment in the room. The goal is not a flawless performance but a visible trail of looking, testing, and revising.
Finish the description with a short summary paragraph that names the work's central problem. Write one sentence about what the piece is trying to do, one about what currently blocks that aim, and one about the evidence you would need to judge it fairly. This summary becomes the spine of the written critique and gives your instructor a fast way to check whether you understood the brief. Read it aloud before moving on; if a listener cannot follow the logic, rewrite it while the session is still fresh. Save this paragraph at the top of the file so the evaluation that follows has a stable reference point.
During the session, protect your attention by keeping the interface simple. Open the critique file, place the cursor at the end, and leave the shortcut ready. Do not reorganize folders, rename files, or adjust settings while people are talking. If the room is loud, sit closer to the speaker and reduce the distance between your mouth and the device. Speak in complete but compact sentences rather than long paragraphs, because a short burst is easier to correct than a rambling one. When someone uses a term you do not know, write it phonetically and ask about it afterward. The note does not need to be beautiful in the moment; it needs to preserve the comment before the conversation moves on.
Multi-person critiques need a clear attribution habit. Say the speaker's name, then the point, then the evidence. For example: Mira, the value range flattens near the center, compare the left edge. This pattern reads well later and prevents the common failure where a strong comment is credited to the wrong person. If two people disagree, capture both positions in sequence and mark the disagreement with a short label. Do not try to resolve it while typing. When the instructor repeats a point, add a second mark rather than rewriting the entry; repetition is a signal about priority. At the end of each speaker's turn, read back the first few terms to confirm the name and the main claim.
Expect interruptions and plan a recovery move. If a sentence is cut off, say resume and finish the thought in one clean sentence. If you lose your place, speak the work's title and the heading again, then continue. If the app inserts an unwanted line break, ignore it until the polish pass; fixing formatting mid-sentence breaks concentration. Keep a small set of spoken commands in mind for structure, such as new heading, new line, and quote, and use them sparingly. When the room gets chaotic, switch to short factual entries and return to interpretation later. A rough but accurate record beats an elegant record that misses the instructor's actual objection.
Close the live capture with a deliberate check. Read the headings in order and confirm that every work discussed has at least one entry. Look for orphan comments that mention a detail but not the piece, and attach them to the right title. Count the number of speakers you recorded and compare that with the number of people who spoke. If a speaker is missing, add a placeholder and fill it from memory before you leave the room. Save the file with the date and session name, then note the three comments you plan to act on first. This five-minute habit prevents the most common loss in studio courses: good feedback that never reaches the next draft.
The polish pass is where a raw transcript becomes a critique someone can use. Work through the file in the Speak-Polish-Type-Edit order: speak any missing transitions, let the app clean filler and grammar slips, type the structural markers, then edit for accuracy and tone. Read one paragraph at a time and ask whether it makes a claim, offers evidence, and suggests a next step. Cut repeated observations and merge comments that belong under the same heading. Voiskey adapts punctuation and formatting to the shape of your speech, so a spoken contrast becomes two clear sentences rather than one tangled line. Keep the student's own voice in the note; the goal is clarity, not a formal essay.
Tone should match the audience. A note for your instructor can carry technical terms and direct judgments; a note you exchange with a peer should be specific and generous. Say the audience out loud before you start the polish pass, then adjust word choice as you go. For a peer, replace verdicts such as weak with observations such as the focal point competes with the border. For an instructor, add the reasoning behind each recommendation and name the principle at stake. If you are writing a self-critique, use the same standard you would apply to a classmate. A short spoken sentence about who will read the note keeps the whole edit pointed in one direction.
Structure turns a pile of comments into a document. Use four headings: context, description, evaluation, and next steps. Under context, state the assignment and constraints. Under description, keep the evidence you gathered. Under evaluation, group comments by principle rather than by speaker. Under next steps, list two or three changes that can be tested before the next class. If a comment does not fit, decide whether it belongs in a separate question file instead of forcing it into the critique. Spoken headings are fast to add and easy to reorder later. A reader should be able to stop after the first screen and still know what the piece is and what you think it needs.
Before you call the draft finished, verify every quotation and attribution. Compare names, titles, and technical terms against your source list, and mark anything you cannot confirm. Voiskey learns the names, jargon, acronyms, and spelling preferences you use, which reduces repeated corrections across a semester of critiques. Read the final document aloud once, ideally to a classmate, and note where they ask a question. Those questions reveal missing context faster than another silent read. Then trim the document by about a tenth; most first drafts carry one extra example per section. The result should be a critique you can defend in conversation, not just a file you submit.
Open your critique note, press the shortcut, and speak while you look at the work. Voiskey places the text at the insertion point in the app you are already using, removes filler and false starts, and adapts punctuation to your sentence, so you can keep observing instead of breaking eye contact to type.
Yes. Speak the rough observations first, then use the polish pass to remove stutters, self-corrections, and grammar slips. Voiskey adapts tone and phrasing to your stated audience, so the same notes can read as a peer exchange or a formal instructor submission after a short edit.
Voiskey learns names, jargon, acronyms, and spelling preferences as you use it. Say unfamiliar studio terms once in context and correct any misspelling in the document; the app uses that feedback in later sessions. Keep a short course glossary beside your critique file so new terms are easy to introduce.
Speak the observation while you view the work, polish the raw draft by removing repetition and repairing structure, type the headings and lists that organize the critique, then edit for accuracy and tone. The sequence keeps observation fast and revision deliberate, which suits a studio session that moves from looking to judging in a short window.

Download Voiskey for Mac and Windows and speak your next draft into place.
Use it across macOS, Windows, iOS, and Android